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
In most cases, the user using the Chia client will only want to make a few Chia transactions with others.
The current Chia client design splits wallet and node into two services, which are usually connected via a websocket-based byte stream.
This websocket call is designed to be called over a decentralized network, which is a bloated and inefficient protocol under LAN conditions or even directly in a local loopback.
Currently, wallets and nodes are synchronized using the same protocols as those used to communicate with the decentralized network, resulting in a significant amount of time consumed to synchronize a wallet's data. By default, for a blockchain like Chia, which currently has close to 300,000 transaction records and continues to grow, a 5-second connection to sync only 32 of those records is unbearable.
So I would like to change the current architecture of communication between wallets and local nodes, for example by considering a protocol that is only used on the LAN or by giving wallets direct access to the nodes' databases instead of using a common protocol.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In most cases, the user using the Chia client will only want to make a few Chia transactions with others.
The current Chia client design splits wallet and node into two services, which are usually connected via a websocket-based byte stream.
This websocket call is designed to be called over a decentralized network, which is a bloated and inefficient protocol under LAN conditions or even directly in a local loopback.
Currently, wallets and nodes are synchronized using the same protocols as those used to communicate with the decentralized network, resulting in a significant amount of time consumed to synchronize a wallet's data. By default, for a blockchain like Chia, which currently has close to 300,000 transaction records and continues to grow, a 5-second connection to sync only 32 of those records is unbearable.
So I would like to change the current architecture of communication between wallets and local nodes, for example by considering a protocol that is only used on the LAN or by giving wallets direct access to the nodes' databases instead of using a common protocol.
Beta Was this translation helpful? Give feedback.
All reactions