Bitroot
  • Bitroot Beginner’s Guide
    • What is Blockchain?
    • Why Use Blockchain?
    • Why Choose Bitroot?
  • About Bitroot
  • Core Products and Solutions
    • Bitroot Protocol Layer
    • BitrootNetwork Parallel Public Chain
    • Bitroot CeDeFi
  • Parallel Architecture and Technical Principles
  • Developer documentation
    • EVM(general)
    • EVM with Hardhat
    • EVM with Foundry
  • Reference
    • Bitroot's EVM RPC
    • Transactions
    • Viewing Tokens in MetaMask
  • Divergence from Ethereum
  • Product Manual and User Guide
    • Bitroot test network information
    • Bitroot Testnet Test Coin Claim
    • Add Bitroot network information
    • Swap
    • Adding Liquidity and Remove Liquidity
  • Token economic model and governance
    • Token issuance and distribution
    • Community Governance and Decision-making Mechanism
  • Participation in ecological co-construction
    • User participation
    • Developer Participation
  • Community, Ecology and Partners
  • Roadmap and future planning
  • Wallets
  • Block Explorers
  • FAQ
  • Brand Kit
  • Bitroot Official Link
Powered by GitBook
On this page
  1. Reference

Transactions

The Bitroot blockchain supports Ethereum Virtual Machine (EVM) transactions,allowing compatibility with Ethereum-based tools and contracts.

from

the address of the sender, that will be signing the transaction. This will be an externally-owned account as contract accounts cannot send transactions.

to

the receiving address (if an externally-owned account, the transaction will transfer value. If a contract account, the transaction will execute the contract code)

signature

the identifier of the sender. This is generated when the senders private key signs the transaction and confirms the sender has authorized this transaction

nonce

a sequentially incrementing counter which indicates the transaction number from the account

data

The input data for contract execution. For simple transfers, this is usually empty.

value

amount of BRC (ETH) to transfer from sender to recipient (denominated in WEI, where 1BRT equals 1e+18wei)

gasLimit

the maximum amount of gas units that can be consumed by the transaction. The EVM specifies the units of gas required by each computational step

maxPriorityFeePerGas

the maximum price of the consumed gas to be included as a tip to the validator

maxFeePerGas

the maximum fee per unit of gas willing to be paid for the transaction (inclusive of baseFeePerGas and maxPriorityFeePerGas)

{
	from: '0x1923f626bb8dc025849e00f99c25fe2b2f7fb0db',
	gas: '0x55555',
	maxFeePerGas: '0x1234',
	maxPriorityFeePerGas: '0x1234',
	input: '0xabcd',
	nonce: '0x0',
	to: '0x07a565b7ed7d7a678680a4c162885bedbb695fe0',
	value: '0x1234'
}

{
jsonrpc: '2.0',
id: 2,
result: {
	raw: '0xf88380018203339407a565b7ed7d7a678680a4c162885bedbb695fe080a44401a6e4000000000000000000000000000000000000000000000000000000000000001226a0223a7c9bcf5531c99be5ea7082183816eb20cfe0bbc322e97cc5c7f71ab8b20ea02aadee6b34b45bb15bc42d9c09de4a6754e7000908da72d48cc7704971491663',
	tx: {
		nonce: '0x0',
		maxFeePerGas: '0x1234',
		maxPriorityFeePerGas: '0x1234',
		gas: '0x55555',
		to: '0x07a565b7ed7d7a678680a4c162885bedbb695fe0',
		value: '0x1234',
		input: '0xabcd',
		v: '0x26',
		r: '0x223a7c9bcf5531c99be5ea7082183816eb20cfe0bbc322e97cc5c7f71ab8b20e',
		s: '0x2aadee6b34b45bb15bc42d9c09de4a6754e7000908da72d48cc7704971491663',
		hash: '0xeba2df809e7a612a0a0d444ccfa5c839624bdc00dd29e3340d46df3870f8a30e'
	}
}
}
PreviousBitroot's EVM RPCNextViewing Tokens in MetaMask

Last updated 1 month ago