The Diamante Laboratory is a set of tools that enables people to try out and
learn
about the Diamante network. The laboratory can build transactions, sign them,
and
submit them to the network. It can also make requests to any of the Aurora
endpoints.
These keypairs can be used on the diamante network where one is required. For
example,
it can be used as an account master key, account signer, and/or as a diamnet-core
node key.
Public Key:
Private Key:
Fund this account on the test network using the friendbot tool
below, note down the wallet details for making transactions
Friendbot: Fund a Test network account
The friendbot is a Aurora API endpoint that will fund an account with 100
DIAMs on the Diamante test network.
This tool can be used to run queries against the REST API endpoints on the Aurora
server. Aurora is the client facing library for the Diamante ecosystem.
The transaction builder lets you build a new Diamante transaction.
This transaction will start out with no signatures. To make it into the ledger, this
transaction will then need to be signed and submitted to the network.
The account responsible for paying the transaction
fee.
The transaction sequence number is usually one higher
than current account sequence number.
The network base fee is currently set to 100 stroops
(0.00001 DIAMs). Based on current network activity, we
suggest setting it to 100 jots. Final transaction fee
is equal to base fee times number of operations in this
transaction.
Enter unix timestamp values of time bounds when this
transaction will be valid.
For regular transactions, it is highly recommended to
set max_time to get a final result of a transaction in a
defined time.
Creates and funds a new account with
the specified starting balance.
Sends an amount in a specific asset to
a destination account.
Sets various configuration options for
an account.
Creates, updates, or deletes a
trustline.
Sets, modifies, or deletes a Data Entry
(name/value pair).
Asset code must be between 1
and 4 characters long.
Asset code must be between 5
and 12 characters long.
This can result in a permanently
locked account. Are you sure you know what you're
doing?
This can result in a permanently
locked account. Are you sure you know what you're
doing?
This can result in a permanently
locked account. Are you sure you know what you're
doing?
Signer will be removed from account if this weight
is 0.
Used to add/remove or adjust weight of an additional
signer on the account.
Asset code must be between 1
and 4 characters long.
Asset code must be between 5
and 12 characters long.
If empty, will delete the data entry named in this
operation.
Note: The laboratory only supports strings.
The account responsible for paying the transaction
fee.
The network base fee is currently set to 100 jots
(0.00001 DIAMs). Based on current network activity, we
suggest setting it to 100 stroops. Final transaction fee
is equal to base fee times number of operations in this
transaction.
The transaction signer lets you add signatures to a Diamante transaction.
Signatures
are used in the network to prove that the account is authorized to perform the
operations in the transaction.
For simple transactions, you only need one signature from the correct account. Some
advanced transactions may require more than one signature if there are multiple
source accounts or signing keys.
Read more about signatures on the developer's site.
Import a tranksaction envelope in XDR format:
Private key for signing
Input a base-64 encoded Transaction Envelope:
External Data Representation (XDR) is a standardized protocol that the Diamante network uses to encode data.
The XDR Viewer is a tool that displays contents of a Diamante XDR blob in a human
readable format.
