Step 01
How should SASCOSM reach you?
Select the primary contact route. The handle field accepts letters, numbers, spaces, plus signs, dots, dashes, underscores, colons, slashes, and @ symbols for real-world handles and profile links.
Phone Direct call or SMS where appropriate.
Telegram Best for fast SASCOSM routing. Public handle: SASC0SM.
Nostr Npub, NIP-05, Primal, or other Nostr-aligned profile.
WhatsApp Useful where phone-led coordination is easiest.
Step 03
Frame the mandate.
The best Bitcoin infrastructure sites qualify use case, assets, institution type, integration need, and support path. SASCOSM needs the same clarity before routing.
Mandate type Select one Bitcoin adoption strategy BUMP / Lightning payments SovereignID / Digi Carta GazAI intelligence workflow Energy infrastructure Escrow / smart-contract work Mining / hardware support Partner or investment conversation Private delivery mandate
Timeline
Settlement preference Not sure yet Bitcoin Lightning BTCPay invoice USDT Escrow Discuss privately
Confidentiality Select one Public context only Commercially sensitive NDA likely required Government / regulated context
Decision needed
Operating context
Step 04
Check the signal before submitting.
Confirm the route, profile, mandate, and timing. This creates a private SASCOSM intake record and Telegram alert for follow-up.
Complete the first three steps to generate the summary.
Do not submit private keys, seed phrases, medical records, trade secrets, or confidential files. If the mandate is sensitive, use this only to request the controlled route.
Draft is local until you submit.