.wasm
file since Beam Virtual Machine (BVM) runs on WebAssembly.Faucet
,' 'Dao-core
,' and inside each folder will be a list of files that will resemble the following:contract.wasm
) and the second allows the wallet to interact with the contract (app.wasm
). We suggest creating a shaders
folder inside the beam
folder with the subfolder with specific apps like faucet
.Faucet
contractFaucet
contract allows users to withdraw or deposit small amounts of Beam coins. Faucet
contract commandsFaucet
inside your shaders
folder as instructed. The app.wasm
file uses Faucet
and contract.wasm
interacts with the blockchain.CID
from the blockchain for this example.Faucet
are compatible with macOS (Terminal Window), Linux (Shell), and Windows (Command Prompt) but for the example below, we will use Terminal Window commands.port 8501
. If your parameters differ from any of the instructions, please adjust them accordingly.IDs
from shaders of faucet types currently deployed on the network. It is possible for more than one shader because the Application Shader (app.wasm
) can interact with several different Contract Shaders (contract.wasm
) of the same type.Faucet
contract, enter the following command:CID
parameter with a different contract ID
that you received in the previous steps.Faucet
contract withdrawal. In total, the action draws 0.061 Beams + the transaction fee, leaving the user with 0.05 Beams.Faucet
limits the amount of Beam coins you can withdraw within a given timeframe. These 'constructor parameters' of the shader specify that you should receive the Beams you have requested when you are under that limit.Magical Error 17
, depending on the contract implementation.Magical Error 17
can also appear for a different glitch within the contract.Facuet
.Faucet
Faucet
, enter the following:contract.wasm
file (located in app.wasm
folder) file to properly deploy the new contract to the blockchain.Faucet
contract has not run within the last 13 blocks, the contract deployment will be successful, and a new contract will issue the return value.Faucet
contract and share the contract ID
with another user!DAO
contractDAO
contractdao-core
contract folder is within theshaders_folder
hierarchy as previously instructed. Both app.wasm
(Faucet
) andcontract.wasm
to deploy your DAO
contract.CID
contract output should resemble the following:farm_view
command:dao-core
contract parameters are as follows:beams_locked
beamX_old
beamX_recent
beamX
"bLockOrUnlock= "in shader_args where : 0 - withdraw Beam , 1 - send Beam
--shader_args role=manager,action=farm_update,cid=3f3d32e38cb27ac7b5b67343f81cf2f8bc53217eb995cc6c5d78ddc5e7b0642b,amountBeamX=635511,amountBeam=10000000,
bLockOrUnlock
=
1
Dao-core
contract parametersdao-core
contract parameters, enter the following command:total_users
avail
received
beam_locked