BLOCKS is an ERC777 token which is compatible with ERC20. One unique feature of BLOCKS is the ability to insert data into a transaction using the "send" function.
- Inserting hashes for data integrity management
- Sending human-readable messages
- Storing immutable NFT metadata
- Simplified crypto ecommerce implementations
Ethereum Mainnet (BLOCKS) 0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB
Ethereum Rinkeby Testnet (BLOCKS) 0x8a6d4c8735371ebaf8874fbd518b56edd66024eb
Polygon / Matic BLOCKS Data (MBD) 0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB
xDai / X BLOCKS Data (XBD) 0x4D6395328104c29b9a5a546ECbbCe2fc75D9b519
Fanton BLOCKS Data (FBD) 0x8a6d4c8735371ebaf8874fbd518b56edd66024eb
Binance BLOCKS Data (BBD) 0x8a6d4c8735371ebaf8874fbd518b56edd66024eb
DAO partners can buy BLOCKS on SushiSwap or Uniswap then deposit BLOCKS into a DAO managed dashboard in exchange API credits. The API credits facilitate faster, cost effective utility for data transactions by utilizing multi-network sidechain tokens.
Faucet provides 2 testnet BLOCKS tokens per day 0x48c0ce9e141f2273501cffa581b2d309a0f24fa6
The following example shows how to insert data into a BLOCKS transaction, also fetching then parsing the data from the blockchain.
Common libraries used for working with Ethereum Smart Contracts.
This example uses Metamask as the Ethereum Provider.
const blocksDataTransaction = () => {
//Connect to Ethereum through the Metamask Provider
window.ethereum.enable().then(provider = new ethers.providers.Web3Provider(window.ethereum));
const signer = provider.getSigner();
//Connect to the BLOCKS Smart Contract via the contract address, abi and provider
const contract = new ethers.Contract(environment.blocksContract, environment.blocksAbi, provider);
let contractSigner = contract.connect(signer);
//Define the data you want to insert on-chain
let data = "Hello, this message is going on-chain!";
let dataConverted = web3utils.toHex(data);
//You can send any amount of BLOCKS tokens with the transaction. BigNumber helps JavaScript deal with large numbers involving BLOCKS' 18 decimals. In this case we are sending 2 BLOCKS.
let amount = new BigNumber(2000000000000000000);
//Now you can call the "send" function by entering a receiving address, amount and the converted data.
let receivingAddress = "0xf0e3ea754D038b979CD0124e2f1A4Bf44f32746a"
contractSigner.send(receivingAddress, amount.toFixed(), dataConverted).then((tx: any)=>{
if(tx){
//View the transaction response and get the transaction hash
console.log(tx)
alert(tx.hash);
}
}).catch((e: any) => {
alert(e);
});
}
For fetching data we need to connect to an Ethereum provider like Infura
const fetchBlocksTransaction = async() => {
//Connect web3 to Ethereum provider
let web3 = new Web3('https://mainnet.infura.io/v3/<infura-api-key>');
//Fetch the transaction id using web3. Insert the transaction id that contains BLOCKS data.
web3.eth.getTransactionReceipt('0x30e2c4a17d5622364f7a66062e56918e8f11d73f814ae11ee0504b27c3f3fd1b').then(res => {
//Call a function to decode the transaction logs, see below.
getLogData(res).then(result => {
console.log(result.data)
//Use web3 Utils to convert the hex data to human-readable data.
let message = web3Utils.hexToAscii(result.data);
alert(message);
});
});
}
const getLogData = (decode) => {
//We need to decode the transaction logs to get the data. This requires the abi of the "send" function, the data and transaction topics. These are passed in as a result of fetching the transaction.
let web3 = new Web3('https://mainnet.infura.io/v3/<infura-api-key>');
let result = web3.eth.abi.decodeLog([{
'type':'address',
'name':'operator',
'indexed': true
}, {
'type':'address',
'name':'from',
'indexed': true
},{
'type':'address',
'name': 'to',
'indexed': true
},{
'type': 'uint256',
'name':'amount'
},{
'type': 'bytes',
'name':'data'
},{
'type': 'bytes',
'name':'operatorData'
}],decode.logs[0].data, decode.logs[0].topics.slice(1));
return result;
}
Have fun exploring and building on BLOCKS with data transactions.
Copyright © 2021 <BLOCKS DAO, LLC>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.