Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2025 Stellar Development Foundation
Subscribe to the Newsletter
By Meta Contracts in Stellar
A set of Meta Contracts apps developers can use to make complex contract invocations without needing to deploy their own contracts
A set of "Meta Contracts" developers can use thanks to a Typescript SDK that makes the process easier. In total, we will introduce 4 (plus the one already created), having different contracts for each type allows developers to just pick the one they need instead of loading one big heavier contract. These contracts are:
Atomic call (the one already created): A contract that executes multiple calls in the same contract call and throws an error if one of them fails, this simulates the way in the classic side an app can execute multiple operations with the safety of rejecting the whole transaction if one of them fails.
Optional succeed call: A contract that lets you send multiple contract calls without where you can decide if it's ok for some of them to fail, an example where this might be useful is when an arbitrager wants to send multiple calls where the goal is to get as many as possible accepting if one or more of them fail.
Conditional calls: A contract that lets developers execute transactions where based on the result from one of the calls it decides what to do next, this allows simulating a classic "if this then that" logic.
Chain flow call: A contract that lets you take the result of one call and inject that result into the following contract call.
Mega call: A contract that has all of the other contract features included and lets the developer use them in the configuration needed, this will be in fact the heavier contract but there are situations where it helps. For example, a developer wants to withdraw from a pool and after that, it wants to get the balances from two assets to later use the result from both calls to fund another different pool, all of that will be possible without that developer needing to upload its own contract.
Yes
$26.4K
If others main protocols use them that will be a success, for example we could use one of them with the Blend front end in order to reduce the amount of simulations calls when fetching all the balances from the RPCs.
Meta contract are inmutable contracts that once they are deployed they are all set and no other plan is needed, once they are public we will follow the same we have done with our other libraries like the Stellar Wallets Kit where we share them in our socials and show them to other developers (that beside using them in our own products).
It all started from a tweet from Tomer that gave us the idea of more "meta contracts" that could be created, the first one was a router that allows developers to "simulate" the atomicity of the classic side on Soroban, but it was created to test an idea from Leigh shared in the Stellar discord regarding fetching multiple balances without needing to do multiple simulations (something useful for our smart wallet). Because it's pretty recent there isn't much traction beside our apps integrating it.
We are a software development company who has been creating both open source and closed source apps in the Stellar network, we are the creators of: xBull Wallet, Stellar Wallets Kit (The wallet connection tool being used in the websites: Stellar Laboratory, Blend Capital, Aqua, FxDAO and others), FxDAO, SorobanDomains, SorobanHub and many others.
Enrique A.
No other submissions.