Skip to content

Latest commit

 

History

History

solana

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
contracts
contracts
 
 
scripts
scripts
 
 
test
test
 
 
.mocharc.json
.mocharc.json
 
 
README.md
README.md
 
 
package.json
package.json
 
 
tsconfig.json
tsconfig.json
 
 
yarn.lock
yarn.lock
 
 

README.md

Solana integration.

Pre-requisites

Solana version: solana-cli 1.14.19 (src:5704dd6e; feat:1879391783)

Solana config example:

Config File: $HOME/.config/solana/cli/config.yml
RPC URL: http://localhost:8899
WebSocket URL: ws://localhost:8900/ (computed)
Keypair Path: $HOME/.config/solana/id.json
Commitment: confirmed

Solang version: v0.3.0

Compile the code

yarn
npm run build

The compiled program .so file and the idl .json file will be put in the test folder. Notes: 

If the tag @program_id is already set in product mode (program id) in the source code, then comment it out.
Before deployment, return it back and recompile.
contracts/ServiceRegistrySolana.sol
//@program_id("AU428Z7KbjRMjhmqWmQwUta2AvydbpfEZNBh8dStHTDi")
contract ServiceRegistrySolana {

Run tests

In a separate window run a validator:

solana-test-validator -r

Setup and run tests:

npm run setup
npm run test

Note that the setup command will create a program .key file in the test folder. If the code has changed, the setup needs to be run again, preferably with the validator turned off / turned on, as it would clear all the data.

Also note that for the correct anchor setup, the necessary payer.key keypair is created during the setup phase.

Deployment

The program is deployed on Solana network with the following addresses:

One can try to run a full service workflow from the service creation to its termination and unbond via the deploy using the following devnet script: devnet_service_management.js.

Deployment procedure

deployer and programKey were created using the solana keygen cli function. For example, for the program Id the following command was used: solana-keygen grind --starts-with AU:1. deployer was made a default keypair path. deployer needs to have a balance that is enough to deploy the program and perform following actions. On the devnet one can use solana airdrop 1 - this will airdrop 1 SOL to the default keypair.

The program bytecode is written into ServiceRegistrySolana.so, and its IDL (ABI) is in ServiceRegistrySolana.json file. Use them to connect to the program on-chain and perform necessary web3 requests.

The devnet and mainnet configurations are located in globals_devnet.json and globals_mainnet.json respectively. In order to run scripts below create a globals.json file for required configuration and endpoint or copy from the specified one.

  • Create a data storage account separately that points to the program Id:
cd scripts
node create_data_storage_account.js
  • Deploy solana program:
cwd=$(pwd)
solana config set --keypair $cwd/deE9943tv6GqmWRmMgf1Nqt384UpzX4FrMvKrt34mmt.json
solana program deploy --url https://api.mainnet-beta.solana.com -v --program-id AU428Z7KbjRMjhmqWmQwUta2AvydbpfEZNBh8dStHTDi.json ServiceRegistrySolana.so
  • Initialize required program parameters:
node initialize.js
  • Add funds to the pda account using the transfer method to finish its initialization.
pda=Gtb5et18X9b63Yex1wpPtKezeXznqDiqJ3zXh1WAqRxK
solana transfer --from $HOME/.config/solana/id.json ${pda} 0.1 --allow-unfunded-recipient