pages / program / venue_acpv3_arc
canister coord://offchain/genie/program/venue_acpv3_arc@v1/89a794e4d9164df2 · v1 · artifact root 0x89a794e4d9164df237020c81cd7d319225066e3497cd06f1427be3cb0dd45cff · previous none (first version) · superroot at publish not sealed yet
sealed cases that reached it: 0 — sealed cases that reached this word (the store counts, never reads)
// generated by genie import from lang/gen/venues-registry.json (acpv3-arc) — a programmable venue: one sale of the twelve hops through it, settled through the vault that pays on its chain, on every chain that vault caps. genie venue_acpv3_arc v1 about "a sale through acpv3-arc (Virtuals ACP v3 on Arc · onchain_market · agentic · eip155:5042 · programmable (adapter lane erc8183-extra)): twelve hops, the legs of the payment, the seller paid on the venue" use venue acpv3-arc use vault vault:taifoon:loop use chain every use product taifoon.api jev.grade use guard owner-arm signer-allowlist value-cap day-cap receipt-check agent sale is "one sale through acpv3-arc" states offer_in classify listed hired delivered graded settled legs accrued split paid recorded refused start offer_in final recorded refused failed refused on tick 60s read GET /v1/venues/:id as venue read GET /v1/match/offers as offers move offer_in -> classify when offer.price > 0 hop classify venue acpv3-arc move classify -> listed hop listed op POST /v1/listings/discover venue acpv3-arc move listed -> hired when hire.paid == true hop hired op GET /v1/listings/:id venue acpv3-arc move hired -> delivered hop delivered op POST /v1/jobs/:jobId/complete move delivered -> graded assure 0.7 meter jev.grade hop graded move graded -> settled act settler signs evm-carrier settle(bytes32) guard owner-arm signer-allowlist value-cap receipt-check via vault:taifoon:loop on every cap 50000 USDC meter taifoon.api hop settled venue acpv3-arc move settled -> legs hop legs move legs -> accrued hop accrued move accrued -> split hop split move split -> paid act releaser signs vault-signer release(bytes32) guard owner-arm day-cap via vault:taifoon:loop on every cap 50000 USDC meter taifoon.api hop paid move paid -> recorded hop recorded op POST /v1/jobs/:jobId/record move * -> refused when venue.known == false refuse open_venue "the venue is not one of the sets" refuse cap_over "the settle is over the vault's per_tx cap" say offer_in "Your offer was read from the venue into the layer" say classify "The offer became one class of the class language" say listed "The offer is listed under the layer’s name" say hired "A buyer created the job and funded its escrow on the venue’s own deployment" say delivered "The seller submitted the deliverable; the escrow waits for the evaluation" say graded "System One graded the delivery" say settled "The escrow released the stablecoin to the seller (or refunded the buyer on a rejection that stood)" say legs "The payment left as named legs that sum to it" say accrued "Each leg sits on its owner’s account" say split "The redirect mode released the share into one batch" say paid "The batch was paid, one signature through the vault" say recorded "The sale is recorded; its proof sits under the superroot" next listed hired "Wait for a buyer: the wall is public, the first paid hire moves the sale" next delivered graded "System One grades the delivery; a reject withholds the share" vault vault:taifoon:loop grid taifoon.api per_call 1 cap USDC every per_tx 50000 per_day 5000000 agreement sale_on_acpv3_arc parties buyer seller layer hops offer_in classify listed hired delivered graded settled legs accrued split paid recorded leg our_fee 5% leg venue_fee 2.5% leg seller_share rest settle via vault:taifoon:loop meter taifoon.api venue acpv3-arc term "the seller is paid on its own venue" term "one payment here is an escrow job on a deployment of the same escrow protocol: created and funded by the buyer, submitted by the seller, settled or rejected or expired" knowledge symptom "the payment did not arrive on the seller venue" caused_by "the settle move stayed behind its guard" fixed_by "arm the vault owner and retry the settle" term "acpv3-arc" is "Virtuals ACP v3 on Arc · onchain_market · agentic · eip155:5042 · programmable (adapter lane erc8183-extra)" term "a payment on acpv3-arc" is "an escrow job on a deployment of the same escrow protocol: created and funded by the buyer, submitted by the seller, settled or rejected or expired" door "Sell on acpv3-arc" as sale product acpv3-arc locale en rule white-label step offer_in "Your offer was read from the venue into the layer" next classify step classify "The offer became one class of the class language" next listed step listed "The offer is listed under the layer’s name" next hired step hired "A buyer created the job and funded its escrow on the venue’s own deployment" next delivered step delivered "The seller submitted the deliverable; the escrow waits for the evaluation" next graded step graded "System One graded the delivery" next settled step settled "The escrow released the stablecoin to the seller (or refunded the buyer on a rejection that stood)" next legs step legs "The payment left as named legs that sum to it" next accrued step accrued "Each leg sits on its owner’s account" next split step split "The redirect mode released the share into one batch" next paid step paid "The batch was paid, one signature through the vault" next recorded step recorded "The sale is recorded; its proof sits under the superroot" step refused "The sale was refused; the reason is named" handoff "the graph has no next step for this case; a person picks up" booking https://cal.com/taifoon meet https://meet.jit.si room genie-acpv3-arc