Caution
This repo has moved to https://github.com/stellar/launchtube
Getting Stellar transactions successfully submitted to the network can be a chore. You've got a lot to think about between fees, sequence numbers, block times, retries, rate limits, ledger limits, and more. This gets even more tricky when trying to submit Stellar smart wallet operations. Soroban contracts can't pay Stellar transaction fees, they maintain nonces not sequence numbers.
The Launchtube service aims to alleviate all of these challenges and complexities by giving you an API which accepts Soroban ops and then handles getting those entries successfully submitted to the network. No XLM or native G-addresses required! Just simulate and sign your Soroban ops, submit them to Launchtube, and we'll handle getting them onchain. Too easy!
Testnethttps://testnet.launchtube.xyzPublichttps://launchtube.xyz
AuthorizationBearer {jwt token}
If you need a Testnet JWT token just open https://testnet.launchtube.xyz/gen.
Submit a transaction
Important
Credits are spent with progressive levels of granularity as the transaction moves through the backend
- Initially upon submission
100_000credits are spent - Assuming your tx simulates successfully, those
100_000credits are refunded and the simulation bid fee is spent - If your tx submission is successful the bid fee is refunded and the final tx fee is spent
This ensures a fair and predictable system without restrictive rate limits by incentiving properly formed transactions
-
feeNumber of credits (stroops) you want to use per operation to submit the transaction
AND
-
xdrTransaction you want submitted as an
XDRencodedString
OR
-
funcxdr.HostFunctionencoded as anXDRString -
authArray of
xdr.SorobanAuthorizationEntryencodedXDRStrings
Content-Typex-www-form-urlencoded
The response of the transaction submission as JSON assuming it was successful. Otherwise a (hopefully) useful JSON error.
Get the remaining credits (stoops) available for your token
String numeric value of the token's remaining credits (stroops)
Webpage form to activate your token to enable usage of the API
-
tokenThe
{jwt token}you were given and wish to activate
The api endpoint used by the GET / webpage form to activate your token
-
tokenThe
{jwt token}you were given and wish to activate
Content-Typex-www-form-urlencoded
AuthorizationBearer {auth token}
If you need an auth token let [email protected] know.
Generate a list of new credit JWT tokens
-
ttlThe number of seconds these tokens should live for
-
creditsThe number of credits these tokens can spend (in stroops)
-
countThe number of unique new tokens to generate (max of 100)
JSON array of tokens which will be what you hand out like candy
Delete a previously generated token
-
subThe JWT
subclaim of the token you want to delete
OK
Run a SQL query on the database
[!CAUTION]
Be careful! I don't do any query validation before running your query so you could easily bork the database with an erroneous query. So don't do that
-
querySQL query you want to run. e.g.
SELECT * FROM Transactions LIMIT 100 -
argsPositional arguments for the query. Include as strings in an array. e.g.
["arg1", "arg2"]
Content-Typex-www-form-urlencoded
JSON array of results from the query (if any) e.g.
[
{
"Sub": "712f3af6061d26ac4c573151e116547a3b58b364fcf5a6df8f1a5916d540cae3",
"Tx": "40833f9c1b6e3187f7ff915a2bbad55e422650a283d3d13d941a5eaf81abaed7"
},
{
"Sub": "712f3af6061d26ac4c573151e116547a3b58b364fcf5a6df8f1a5916d540cae3",
"Tx": "f5b4d4638944ffab6ca693fe4036275c4822dd46e7e0f558a4e53a38f704fb45"
},
...
]Sub is the token's sub claim and Tx is the transaction hash
Get information about the sequencer Durable Object. You very probably don't ever need to run this. It's really just for system maintainers doing health or debug checks.
Review the endpoint code for available params.
JSON object with information about the sequencer. Again, review the code for the exact shape of the response.