Chasm Database is powered by Chromia for data transparency layer.
Cluster: Pink
Dapp: chasm_opml
BRID: A870F5744F8C4EDFE5AAD5556B1B4DA1DCC6FB53B0E8CFAB84F9155A51D1042C
chr installshould installed FT4 intosrc/lib/ft4- create a file
.chroma/chasm-testwith this test key
privkey=0101010101010101010101010101010101010101010101010101010101010101
pubkey=031b84c5567b126440995d3ed5aaba0565d71e1834604819ff9c17f5e9d5dd078f
- Update variables
Update pubkey in development.rell
object owner {
mutable address: pubkey = x"031b84c5567b126440995d3ed5aaba0565d71e1834604819ff9c17f5e9d5dd078f";
}
In main.rell Update the line
// FROM
import production.{owner};
// TO
import development.{owner};
Update chromia.yml
blockchains:
prompt:
module: developmentchr buildto ensure build has no issuechr test
Before running the script, make sure the local client is up.
chr node start
# if needed to wipe db
chr node start --wipe
# Can update code via update command
chr node updatebun i
bun run nodejsChromia does not have official python client, so we are using the Postchain API.
python script/query_data.py # bun run pythonMake sure setup ~/.chroma/config with private key at ~/.chroma/chasm-production
key.id = chasm-production
# Deployment
chr deployment create --settings chromia.yml --network mainnet --blockchain prompt
# Update
chr deployment update --network mainnet