WeaveVM - Dymension.xyz: DA client for RollAP
Description of WeaveVM integration as a Data Availability client for Dymension RollApps
Last updated
Description of WeaveVM integration as a Data Availability client for Dymension RollApps
Last updated
WeaveVM provides a gateway for Arweave's permanent with its own (WeaveVM) high data throughput of the permanently stored data into .
Current maximum encoded blob size is 8 MB (8_388_608 bytes).
WeaveVM currently operating in public testnet (Alphanet) - not recommended to use it in production environment.
Understand how to boot basic Dymension RollApp and how to configure it.
How it works
and to enable tls next fields should be add to the json:
web3_signer_tls_cert_file
web3_signer_tls_key_file
web3_signer_tls_ca_cert_file
Web3 signer
in rollap-evm log you will eventually see something like this:
Obtain test tWVM tokens through our for testing purposes.
Monitor your transactions using the .
You may choose to use WeaveVM as a DataAvailability layer of your RollApp. We assume that you know how to boot and configure basics of your dymint RollApp. As an example you may use
repository.
Example uses "mock" DA client. To use WeaveVM you should simply set next environment variable
before config generation step using init.sh
export DA_CLIENT="weavevm" # This is the key change
export WVM_PRIV_KEY="your_hex_string_wvm_priv_key_without_0x_at_the_beginning"
init.sh will generate basic configuration for da_config in dymint.toml which should look like.
da_config = '{"endpoint":"https://testnet-rpc.wvm.dev","chain_id":9496,"timeout":60000000000,"private_key_hex":"your_hex_string_wvm_priv_key_without_0x_at_the_beginning"}'
In this example we use PRIVATE_KEY of your WeaveVM address. It's not the most secure way to handle transaction signing and that's why we also provide an ability to use web3signer as a signing method. To enable web3signer you will need to change init.sh script and add correspondent fields or change da_config json in dymint toml directly.
e.g
da_config = '{"endpoint":"https://testnet-rpc.wvm.dev","chain_id":9496,"timeout":"60000000000","web3_signer_endpoint":"http://localhost:9000"}'
is a tool by Consensys which allows remote signing.
Using a remote signer comes with risks, please read the web3signer docs. However this is a recommended way to sign transactions for enterprise users and production environments. Web3Signer is not maintained by WeaveVM team. Example of the most simple local web3signer deployment (for testing purposes): Example of used configuration: