RPC
Using and interacting with Soroban RPC is an important part of the smart contract development lifecycle.
Guides in this category:
📄️ Generate ledger key parameters with a symbol key using the Python SDK
In the [increment example contract] stores an integer value in a ledger entry that is identified by a key with the symbol COUNTER. The value of this ledger key can be derived using the following code snippets.
📄️ Retrieve a contract code ledger entry using the JavaScript SDK
When you deploy a contract, first the code is "installed" (i.e., it is uploaded onto the blockchain). This creates a LedgerEntry containing the Wasm byte-code, which is uniquely identified by its hash (that is, the hash of the uploaded code itself). Then, when the contract is "deployed," we create a LedgerEntry with a reference to that code's hash. So fetching the contract code is a two-step process:
📄️ Retrieve a contract code ledger entry using the Python SDK
When you deploy a contract, first the code is "installed" (i.e., it is uploaded onto the blockchain). This creates a LedgerEntry containing the Wasm byte-code, which is uniquely identified by its hash (that is, the hash of the uploaded code itself). Then, when the contract is "deployed," we create a LedgerEntry with a reference to that code's hash. So fetching the contract code is a two-step process: