Solana tx begins when a user connects to an app and intends to do a tx on that app.
For e.g. when you click 'Swap' on Jupiter
The app then verifies the user wallet balance and other metadata, and constructs the tx
Each tx includes:
a) Header: indicating which accounts must sign the tx
b) Instructions: the operations that must be performed during this tx
c) Hash of a Recent Block: to prevent stale txs
d) Access List: the accounts being read from or written to
The app then sends the tx to the user, who signs the tx with their private key (via a wallet), and sends it back to the app
2/11
SENDING TO RPC
The signed tx is sent to an RPC node (like @heliuslabs) that sanity checks the tx by verifying that the signatures are valid, tx format is correct, etc.
RPCs can be thought of as gateways to interact with and read data from the network.
They run the same software as full validators but with different settings, allowing them to accurately simulate txs and maintain an up-to-date view of the current state of the chain
Here are 3 features that could unlock mass adoption and bring MILLIONS of new users to crypto. 🧵
For an average Joe to start using crypto, 3 things need to be true.
dApps should be:
• Super easy to use (crypto hides in background)
• Cheap & Fast
• Interoperable - Users should be able to transfer their assets between any 2 dApps (on any chain) easily
zkSync does all 3:
1. Native Account Abstraction
Let's be honest - we can't expect to take crypto to the masses by asking them to remember 16 words for their wallets.
Creating an account should be as easy as signing up with Gmail.