Repository navigation
v1.135.158 NETFORY WEB4.0 Network
Wallet fixes
-
Fixed: first transaction from a fresh wallet failed (name registration, first send). For a wallet with no outgoing transactions the node replies
404("wallet not yet on chain"), which the client should read as nonce 0. Instead, the REST client treated any HTTP status as a failure and failed over to a backup node - alwaysnode0.smartholdem.io. If that host didn't resolve (Windows DNS error 11001), the original404was lost and the wallet surfaced "Dns Failed" and refused to sign. Now a4xxresponse (except429) is treated as a final answer with no failover, so a new wallet correctly starts at nonce 0 and signs its first tx with nonce 1. -
Node failover no longer pinned to node0. The backup node is now the next node in the pool after the active one, so a single unreachable host can't break every fallback.
-
Fixed ERR_BAD_NONCE on send. The in-flight nonce cache used to live forever and advance on every "accept" from any node (including a local pool whose tx the network later rejected), so the wallet could sign with a stale, overshooting nonce (e.g. 1255 while the chain was at 1250). The cache is now time-limited (60 s), is cleared whenever a broadcast is rejected, and the chain nonce is authoritative again after the window - the next attempt always starts from the node's current nonce.
Additional tools:
- NetDrop (fast file exchange) https://github.com/NETFORY/NetDrop/releases/tag/0.6.7
- DEV Hub protocol tool (dev:// decentralized "github") https://github.com/NETFORY/git-remote-dev/releases/tag/1.55.47