Build: transactions, rent, one platform per wallet
Build asks your wallet for one approval and sends three transactions in order. Here is what each one does and what it costs.
The batch
- createPlatformConfig
- 0.5 SOL to the Shader vault
- Memo: curveshader:build:<platform>
- createPlatformCurveRule
- updatePlatformCurveRule, group 0
- updatePlatformConfig
- restrictCurveParam = 1
Before you sign, the editor simulates transaction 1 on Solana and checks the rule group against the SDK's validator. Transactions 2 and 3 need the platform to exist, so they are checked, not simulated.
Cost
| PlatformConfig rent | about 0.0054 SOL (944 bytes) |
| Curve rule rent | 0.002 to 0.034 SOL, by the number of constraints |
| Network fees | under 0.0001 SOL with priority fees |
| Build fee | 0.5 SOL, used in full to buy and burn $SHADER |
One platform per wallet
The PlatformConfig address is derived from the admin wallet, so one wallet can administer one platform. The wizard checks this before you sign. For a second pad, connect a second wallet.
Sending and confirming
The three signed transactions are sent one at a time. After each send the site polls getSignatureStatuses until the transaction is confirmed, then sends the next. Public RPC nodes rate-limit confirmTransaction, so polling is the reliable path. If a transaction fails, the batch stops and the error is shown with its Solscan link.
