You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TCK looks for a JSON-RPC server on localhost port 80. Port 80 is problematic because you need to run as super-user, which is awkward. It would be better to pick a port above 1024, such as 8545 (This should be the default JSON-RPC server port). Both the host and port of the JSON-RPC server should be trivially configurable on the TCK, to support scenarios where the TCK is on one machine and the JSON-RPC server on another. The project should also document which port is the default port so that all SDKs can use the correct port by default.
The text was updated successfully, but these errors were encountered:
Added a line talking about the default json rpc server url, and where it can be configured in the README
this commit fixes issue hiero-ledger#325
Signed-off-by: LukeBair <74842241+LukeBair@users.noreply.github.com>
The TCK looks for a JSON-RPC server on localhost port 80. Port 80 is problematic because you need to run as super-user, which is awkward. It would be better to pick a port above 1024, such as 8545 (This should be the default JSON-RPC server port). Both the host and port of the JSON-RPC server should be trivially configurable on the TCK, to support scenarios where the TCK is on one machine and the JSON-RPC server on another. The project should also document which port is the default port so that all SDKs can use the correct port by default.
The text was updated successfully, but these errors were encountered: