Skip to content

v1.135.170 NETFORY WEB4.0 Network

Choose a tag to compare

View all tags
@technologiespro technologiespro released this 23 Sep 05:50
1.135.170
7a3218b

NETFORY Wallet over iroh

Wallet transport moved to iroh (SHIP-44). The wallet now talks to sth-core nodes directly over the iroh QUIC mesh instead of HTTPS RPC. Three built-in api://…/sth-core nodes form the primary pool; the legacy HTTPS pool is kept only as a fallback when no iroh node is reachable. Every response is signed by the node's key (pdata, Ed25519 = EndpointId) and verified client-side. Failover goes iroh -> next iroh node -> clearnet; 429/503 switch nodes immediately. Node auto-selection prefers iroh nodes by latency and skips any node lagging more than 5 blocks.

Live push events instead of polling. A single persistent stream (sth/events/1) delivers balance, tx, mempoolTx and block frames as they happen. Balance updates and incoming-transfer notifications are instant, pending transactions appear in history right away, and the dashboard shows a pulsing LIVE badge with the current network height. Background polling drops to a 2-minute safety check while the stream is up; on reconnect the node replays anything missed since the last seen height.

Nonce fixes. First transaction from a brand-new wallet no longer fails (a 404 wallet not on chain from the active node was being masked by a DNS error from the backup node). The wallet now also accounts for the node's unconfirmed pool (/transactions/unconfirmed?senderId=) and, if a node still rejects with ERR_BAD_NONCE, re-signs once with the nonce the node expects.

SHIP-14 token balances. Non-zero token balances (symbol, name, logo, amount by decimals) are shown on the wallet dashboard and update live from the balance stream.

Nodes screen. P2P tab is now first and lists the iroh pool with an iroh badge, latency, height and stream status (LIVE/reconnecting/legacy). Automatic detection of a local localhost:4003 node has been removed - add it manually under "Custom nodes" if you still need it.

Fixes. Moving the data folder no longer fails on the locked smartnet_db (os error 33) - the database stays in place and locked cache files are skipped instead of aborting the transfer.

README

image

Additional tools:

Assets 3
Loading