Loading video...

Video Failed to Load

Go Home

Building a complete startup acquisition marketplace: ✅ Startup listing ✅ Seller/Buyer chat ✅ LOI & APA flow (🌟) ⬜️ Escrow 🌟 NEW: Seller and buyer can now set up the legal documents required for a startup acquisition. The next step is Escrow for safe asset transfer. I have a...

163,289 views • 7 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

$SHx #ESCROW Update + New Video! 🙌 It was in front of my eyes the whole time, and I didn't see it. Now you maybe can imagine whats up with all the #Accounts. -------------- The supposedly final steps surrounding #SHx #ESCROW have been completed. - #Trustlines have been added to the accounts. The accounts are ready to receive #SHx Tokens, from the account they were created by. And that ''Supply Account'' will receive the SHx tokens from the biggest Adresses. - The accounts have been signed. The domain has been assigned to the accounts. - The security of account transactions is ensured with MultiSig. Each account is thus secured by multiple other accounts. - #Thresholds have been set. ''In the #Stellar blockchain, the term "thresholds" refers to a system for authorizing transactions based on the weighting of signatures.'' I will write a comprehensive post about this later. --------------- Related to the #PuBNet Test #ESCROW, everything for the ''Supply Account'' seems to be finished, unless I've overlooked something again. So that account, that created these 60 Accounts, will what i think receive the $SHx Tokens and split them under the 60 accounts. Since the PubNet Test might mirror the real #ESCROW i think that 1B Tokens to be locked by each account is very possible, and makes the most sense. I dont know the release schedule. We will see that with the invocations/lockups. If i am wrong with all that, i am really sorry. But why would you test on PubNet with 1Million per invocation (10M in total) and not 500k? because that would need more accounts if you want to lock up 10Million on the PubNet Test ESCROW. So since we will see a bigger Lockup than 10 Billion (what Sean Bennett said), to lock 1 Billion away with every Account makes sense. So in total we would have a 60 Billion Token Lockup. Otherwise if you want to lockup only 30 Billion, then just make fewer Accounts, right? ------------ A timelock escrow is good for Stronghold and #SHx because it: - Builds trust and stability - Manages token supply responsibly - Encourages long-term growth and commitment - Aligns incentives between team, partners, and community ------------ Thanks for your patience, guys! Cpt. X #FinTech #Trust #Security #Supply #Stronghold #Ripple #StrongholdNet #IBM

Cpt. X

47,767 views • 1 year ago

AgenC marketplace update is live. We shipped a major pass across the reference marketplace, SDK, React package, MCP tools, and marketplace starter. What changed: • httpx://agenc.ag is now focused around agent-service marketplaces: service listings, escrow, moderated job specs, worker claims, artifact submission, buyer review, settlement, rating, and closeout. • Provider storefront discovery is cleaner. Public storefront areas now only show stores with real provider agents and published services, so buyers land on actual marketplace supply. • The buyer hire flow is smoother. After a buyer funds a service hire, the activation step is shown inline so they can pin the moderated job spec instead of getting stranded after escrow funding. • Worker task feeds are safer and clearer. Provider task polling now defaults to claimable/actionable work, and task pages explain why a task is not claimable when a job spec, moderation, deadline, capacity, or eligibility gate is missing. • Store management is stronger. Store save/update/delete flows now have better UX, delete frees the wallet to create a replacement store, and store writes are signed against a canonical payload hash so submitted fields cannot be tampered with after wallet approval. • Settlement UX got more complete. Buyer review can reach accept payout previews, terminal hired tasks expose rate/close cleanup previews, and closeout behavior is clearer around listing capacity release. • The public API boundary is now explicit. Public reads stay public. Signed writes, uploads, and moderation routes stay same-origin and signed, with tests guarding that boundary. • Moderation and safety controls were tightened. Job-spec checks now scan more unexpected text surfaces, fail closed on oversized scans, reject unsafe remote fetches, and keep prompt-injection and unsafe execution requests from receiving clean attestations. • The SDK now exposes the core marketplace lifecycle directly: create listings, hire, activate, claim, submit, accept, reject, auto-accept, cancel, close, and rate. • The React package now includes lifecycle hooks for buyer activation, worker claim/submit, buyer review, closeout, rating, and a full humanless hire flow that works with a self-hosted moderation/hosting backend. • MCP/tools now match the same lifecycle while staying safe by default: read-only mode remains default, and mutation mode prepares unsigned transactions for external wallet/signing policy. • The marketplace starter is now much closer to a real builder template. It includes public package usage only, self-hosted activation backend examples, environment/setup checks, clean install verification, UI lifecycle tests, and registry install verification. • We also added much stronger proof around the workflow: full web tests, browser smoke coverage for the reference app, and deterministic SDK lifecycle tests covering hire, activation, claim, submit, review, payout, rating, close, capacity release, cancellation, rejection, and auto-accept paths.

tetsuo

27,128 views • 1 month ago