Beta API
The Beta API is in... beta.
Last updated
The Beta API is in... beta.
Last updated
Note: The Beta API is currently disabled for some much-needed updates. If you need to use it, please contact us.
Beta currently offers information about singletons.
Leaflet can be acessed at https://kraken.fireacademy.io/beta/
or https://kraken.fireacademy.io/{api-key}/beta/
. Billing is based on the number of returned results, with each result costing 42 credits. Each request consumes at least 42 credits:
request_cost = 42 * max(num_results, 1)
For a better experience, please refer to this generated page.
Wondering what's hidden behind a singleton's inner puzzle hash? Use this endpoint to find out!
The reason Beta was invented.
Is Beta up-to-date or a trillion blocks behind?
Warning: Not suitable for heptapods.
Beta stores all revealed inner puzzles of singletons. Use this method to get it from the corresponding puzzle hash. The puzzle will be returned as a hex string.
The inner puzzle hash
"6b665c0e059050f71a1c3e8a7d5b58e4e1d7abbd02d937e9b5ab5abfd7f8eaba"
OK
1
true
Singletons are like souls - when a coin dies (gets spent), they might move on to a new coin or disappear (melt). Beta views these transitions as changes of state. This endpoint takes multiple optional arguments and returns the states that match the criteria. Most body parameters are self-explanatory: if they match a field of the returned struct model (e.g., 'height' or 'launcher_id'), they act as filters. Only states with the specified values will be returned. The first special parameter is 'limit' - by default, this function returns 100 results at most. Use this parameter to tweak this value. 'order_by' can be 'coin_id', 'header_hash', 'height', 'parent_coin_id', 'puzzle_hash', 'amount', 'launcher_id', or 'inner_puzzle_hash'. The default ordering is ascending, but that can be changed by setting the 'order' parameter to 'desc'. If your query returns more than 100 results and you need all of them for some reasons, you can also use the 'offset' parameter. Note: Two singleton states CAN have the same coin id but a different 'melted' value - the primary key is a composite one: (coin_id, melted)
The arguments (see description for more details)
1
"625799464319c8703ac2d0664af98cf45b9b306f7dcf717b1070d170bb5916a9"
"796c33c3905150e649211fdd9ed42c7c418758c30c321271973a7c792a5bd403"
2174316
"6b665c0e059050f71a1c3e8a7d5b58e4e1d7abbd02d937e9b5ab5abfd7f8eaba"
"f4dd6f4ec490974f7eb98223748f47340a9e9363b4c2dccc1932cdbbc54d03fd"
7
1
"desc"
"amount"
"e9676e8ce096c5be27dee2fbf2120054d206e4df2de9ef59c24a651d3c558c95"
"0a5a9c760970ebcc094c6f9faa3d9730f066c7a8f7450841a94fc4fd59229bc2"
OK
1
true
Beta constantly syncs to the blockchain by fetching the latest blocks. This function returns information about the latest processed block (the one with the biggest 'height' value).
OK
1
true
Beta constantly syncs to the blockchain by fetching the latest blocks. This function returns information about the latest processed block (the one with the biggest 'height' value).
OK
1
true
Beta constantly syncs to the blockchain by fetching the latest blocks. This function returns information about the block at the given height.
The height
2000000
OK
1
true
Beta constantly syncs to the blockchain by fetching the latest blocks. This function returns information about the blocks with height in [start, end).
The start and end heights
2000001
2000000
OK
1
true