Product demo
Watch the complete launch flow, from token configuration through the atomic create, buy, and Streamflow lock transaction.
The demo enters token metadata, selects a 0.1 SOL initial buy, configures a seven-day lock for 51 percent of the purchased tokens, reviews and signs the atomic launch, then verifies the created token and finalized transaction.
Overview
The browser wizard requires GitHub authentication before it uploads metadata or requests a launch transaction. A Solana wallet is connected separately and keeps control of every wallet signature.
Token creation uses pump.fun infrastructure. The browser validates a server-built transaction that creates the token, executes the initial buy, deposits the selected amount into a Streamflow time lock, and deactivates the launch lookup table in a single atomic transaction.
Launch flow
Authenticate
Sign in with GitHub. This creates the session required by launch and metadata endpoints.
Configure
Add token metadata, choose an initial SOL buy, and select the time-lock duration and percentage.
Prepare the lookup table
The first wallet signature creates an address lookup table that lets the launch fit in one transaction.
Approve the atomic launch
The second signature creates the token, executes the buy, deposits the Streamflow lock, and deactivates the lookup table in one transaction.
Verify receipts
Check the launch signature and lock state independently before relying on any platform label.
Partial failure
If the lookup table lands but the atomic launch cannot complete, no token exists. The wizard walks the same wallet through deactivating and closing the table, then unlocks a fresh launch. There is no state where a token exists without its recorded lock.
Estimated costs
The review screen estimates the initial buy plus network, account-rent, protocol, and priority costs. Actual charges can change. Read the transaction simulation and wallet prompt before approving.
Lock behavior
The current builder creates a self-directed Streamflow token lock. It uses the connected wallet as sender and recipient, disables cancellation and transfer permissions, and schedules the locked amount for release at the end of the selected period.
- The lock amount is computed from the exact token quote of the launch buy.
- A percentage below 100 leaves the remainder liquid.
- Streamflow fees mean the deposited amount can be slightly below the selected percentage.
- The recorded percentage is recomputed from the finalized deposit and the tokens acquired in the launch transaction.
- LCKD does not offer an unlocked launch path.
Streamflow documents token locks as inaccessible before the unlock date. Review the current product documentation at Streamflow Token Lock. Protocol behavior and fees can change.
Trust surface
Every program a launch touches is pinned in the open-source client and server code. A transaction that references anything else is rejected before signing and again at receipt verification.
| Token lock | Streamflow v13 | strmRqUCoQUgGUan5YhzUZa6KqdzwX5L6FpUxfmKg5m |
| Token creation and buy | pump.fun | 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P |
| LCKD platform token | SPL mint, no mint or freeze authority | 7UTubJ3W6JWwLUj82B9LgHFDmc8wFWtSNLis6u8epump |
What LCKD cannot do
- Cancel, modify, transfer, pause, or seize any lock. Locks are contracts between the launcher wallet and the Streamflow program; LCKD holds no admin key over them.
- Custody tokens or liquidity. The lock escrow is owned by the Streamflow program, and liquidity is pump.fun's own bonding curve and graduation. There is no LP position held by LCKD.
- Change a launch after review. The server builds the transaction, but the browser independently re-validates every instruction byte for byte before the wallet signs, and the finalized receipt is verified again before anything is recorded.
Execution guarantees
A signed Solana message is immutable, so nothing can change between simulation and execution. The buy carries a hard spend cap and the lock amount is fixed in the instruction rather than recomputed at execution. If the market moves past the cap, the whole transaction fails and no token exists. Any launch fee executes inside the same transaction under the same rules.
The validation code is public. Read it at github.com/rickzsol/lckd.
Verify independently
LCKD records submitted signatures and displays schedule summaries. Those records are convenient indexes, not an on-chain audit. Before relying on a lock, verify the mint, token amount, sender, recipient, cancellation settings, transfer settings, and unlock time using independent tools.
Profile labels
GitHub sign-in proves control of a GitHub session at authentication time. A submitted repository or product URL is a profile link, not proof of code quality, ownership, availability, or token safety.
Directory labels such as Locked, Verified, Builder, or Shipped are platform metadata. They are not endorsements, audits, or guarantees. Always inspect the linked accounts and on-chain records yourself.
For buyers
A valid lock restricts only the deposited amount for its configured period. It does not restrict other wallets, prevent mint or freeze authority abuse, secure liquidity, guarantee development, or prevent price loss.
- Confirm the mint address across every page and explorer.
- Check the exact locked amount, percentage, and unlock date.
- Review holder concentration, authorities, liquidity, and Token-2022 extensions.
- Treat badges, boosts, repository links, and product links as signals, not proof.