Gno mobile blogpost 2023.09.29 #30
Conversation
v1 of the blogpost
v2 blog draft
|
|
||
| *Why is this important?* | ||
|
|
||
| If you want to add a new message to a blockchain, you need to actually interact with it (the blockchain) and update its state with the new message. However, if you just want to browse through the messages, you can execute the Render function locally without needing to use your network and, at the same time, get the results much faster. This is because the node runs locally on the mobile device without needing to spend crypto coins to get a remote node to do the operation for you. |
There was a problem hiding this comment.
With the node running locally, how long do you anticipate a sync to take (and is memory a concern?), or do you imagine this application to serve more like a light client where it will communicate externally to either a full or archive node and not store any of the state on the device itself?
There was a problem hiding this comment.
The plan for V1 is a light client. In this section, we discuss future plans to experiment with the full node on the mobile. In this case, you are correct that it is a concern how much time it can require to sync the blockchain onto the mobile device (or if it is possible to only sync part of it). This needs to be investigated.
Co-authored-by: Manfred Touron <[email protected]>
|
@moul @costinberty are we ready to publish? |
|
@michelleellen for me, the content is OK |
PR for the GnoMobile blogpost. Please consider Squash Merge