Block Collider & Borderless Markets

Documentation, market information and support for Miners and Market Makers.

Get Started Forum & Support Developer API

Examples of Active Uses of Timble

Coinbase Tx

This output tx represents the mining reward for winning a block (just the coinbase tx without any other tx's) indicating that 16 NRG is now owned by the winning miner. That user is indicated as "5afb9171eb4ad484b4518b9e192c89df83949616b2e8733748146720e85062cb" which is the winning miner's address hashed twice by the blake2bl function. In order for "5afb9" to spend this output, they need to provide three arguments in their spending input:

  • The signature of the new tx that will be spending the NRG from this output, signed by this user's private key
  • The public key of the respective user's (winning miner) private key
  • Their address hashed once by the blake2bl function

OP_BLAKE2BL, OP_EQUALVERIFY, and OP_CHECKSIGVERIFY are the opcodes that automatically hash, compare, and verify that a given user has ownership over, and therefor the ability to spend, a given amount of NRG.

"txs": [

    {
        "hash": "c77679d8f8711a32df896fe787e6083627e667c61111b5b544d3582b960e5a13",
        "inputs": [],
        "outputs": [
            {
                "value": "16",
                "unit": 1,
                "scriptLength": 109,
                "outputScript": "OP_BLAKE2BL 5afb9171eb4ad484b4518b9e192c89df83949616b2e8733748146720e85062cb OP_EQUALVERIFY OP_CHECKSIGVERIFY"
            }
        ]
    }

]

NRG Transfer Tx

This is an example of a block with a coinbase Tx as well as an NRG transfer (which includes both the input and output data).

TX - 1
This is the coinbase transaction, rewarding a miner (5afb9), with the NRG block reward along with all NRG fees. The fees paid by the user wishing to transfer are 1.001 NRG, which is made up of 0.001 NRG as a Tx fee and 1 NRG as an incentive fee that the sending user added for the miner to prioritize their transfer.
Identical to the first example, in order for "5afb9" to spend this output of 17.001 NRG, they need to provide the previous three arguments in their spending input which involve using the OP_BLAKE2BL, OP_EQUALVERIFY, and OP_CHECKSIGVERIFY opcodes.

TX - 2
This is the NRG transfer Tx, which shows the tx hash (6402a8...) and where the NRG being transferred is coming from. In this case, the NRG being sent is coming from tx hash "c7767...", which is the coinbase tx from the first example. This means the original winning miner is sending NRG to the user indicated by "c72d0..." (which is the public key of the recipient hashed twice by the blake2bl function). Notice that the value is 16 that is being accessed for the transaction, but the amount being sent is ultimately 14.999 NRG due to fees.

Notice that in the input section, the sending user includes the signature of the new tx that will be spending the NRG from the output from the tx where he is sending from, signed by this user's private key, the public key of the sending user's private key, and their address hashed once by the blake2bl function.

At this point, similar to the coinbase tx's, in order for c72d0 to spend this 14.999 NRG, they need to provide the previous three arguments in their spending input which involve using the OP_BLAKE2BL, OP_EQUALVERIFY, and OP_CHECKSIGVERIFY opcodes.

"txs": [

    //TX - 1

    {
        "hash": "6ae3aeb24a31d64fe53a24cf476ee7fcc4bb50e03b5a24f1503e0ea3a571770b",
        "inputs": [],
        "outputs": [
            {
                "value": "17.001",
                "unit": 1,
                "scriptLength": 109,
                "outputScript": "OP_BLAKE2BL 5afb9171eb4ad484b4518b9e192c89df83949616b2e8733748146720e85062cb OP_EQUALVERIFY OP_CHECKSIGVERIFY"
            }
        ]
    },

    //TX - 2

    {
        "hash": "6402a80532121b0548a86a09274ef5162e6d3a084a554a91367d7f8ef0cf8242",
        "inputs": [
            {
               //necessary values to send NRG from previous transaction, including total amount getting sent (including fees to the miner).
               "outPoint": {
                    "value": "16",
                    "hash": "c77679d8f8711a32df896fe787e6083627e667c61111b5b544d3582b960e5a13",
                    "index": 0
                },
                "scriptLength": 262,

                //[signature] [public-key] [blake2bl(address)]
                "inputScript": "efaed417973467ecf6386a4aec90d215dab0e64f72461da2b1862234ba8542bb5f19476d964d8f331a5b359a826679b490450902adc64b0753fcacbd6696f9a400 02d2f8226c9847cd5943739e3e65f474244b660624ece913141002d9c86ef34a7e 1c9573893865fcb497c6f4ab420a73c05106cc398a4c9fe2ce36b916b2c3624e"
            }
        ],
                                //final amount going to recipient
        "outputs": [
            {
                "value": "14.999",
                "unit": 1,
                "scriptLength": 109,
                "outputScript": "OP_BLAKE2BL c72d0cb74ba65b3cdaec173fe7f24f9d30b7cdf29a21dfafdc069886bf703671 OP_EQUALVERIFY OP_CHECKSIGVERIFY"
            }
        ]
    }
]

Maker Script

Coming soon...

Taker Script

Coming soon...

Updated about a year ago

Examples of Active Uses of Timble


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.