Pact Community Organization

🧭 Pact Quest #8 opens today at 14:00 UTC — Pact and time.

Contracts constantly need to know how far apart two moments are: has a deadline passed, has a window lasted long enough? Which Pact builtin takes two time values and returns the number of seconds between them?

(lowercase, hyphenated, exactly as you would write it in Pact — the name only, no parentheses)

Read the Kadena CE docs — the answer is one page away:
📖 kda-chain.org/docs/pact-5/ti…
📖 kda-chain.org/docs/smart-con…

Claim from 14:00 UTC → pact-community.org/token, select quest-8
100 PCO · one claim per account · closes Fri 20 Nov, 12:00 UTC

🧭 Pact Quest #7 opens tomorrow at 14:00 UTC — Pact keysets: how many keys must sign?

A Pact keyset lists public keys and a predicate that says how many of them must sign. Which built-in predicate is satisfied as soon as at least two of the keyset's keys have signed, however many keys it holds?

(lowercase, hyphenated, exactly as you would write it in Pact — the name only, no parentheses)

Read the Kadena CE docs — the answer is one page away:
📖 kda-chain.org/docs/smart-con…
📖 kda-chain.org/docs/pact-5/ke…

Claim from 14:00 UTC Sunday → pact-community.org/token, select quest-7
100 PCO · one claim per account · closes Fri 6 Nov, 12:00 UTC

—

✅ Pact Quest #6 is closed — Thank you all.

The answer was with-default-read. It reads a table row and binds the columns you name, but when the key is missing it takes them from a default object instead of aborting. That is how a balance reads as 0.0 before an account's first credit.

The ones it is easily confused with:
• with-read — same shape, no fallback: a missing row aborts the transaction
• read — returns the whole row, also aborts on a missing key
• select — scans a table with a where clause rather than reading one key
📖 kda-chain.org/docs/pact-5/da…

Questions: t.me/PactCommunityO…
Free and valueless. Never sold.

#Pact #Kadena kadena:native @KdaCed #SmartContracts

🧭 Pact Quest #6 opens tomorrow at 14:00 UTC — Pact tables, and the row that isn't there.

Reading a row that does not exist makes a Pact transaction fail. Which built-in reads a row but falls back to values you supply when the key is missing?

(lowercase, hyphenated, exactly as you would write it in Pact — the name only, no parentheses)

Read the Kadena CE docs — the answer is one page away:
📖 kda-chain.org/docs/smart-con…
📖 kda-chain.org/docs/pact-5/da…

Claim from 14:00 UTC Sunday → pact-community.org/token, select quest-6
100 PCO · one claim per account · closes Fri 23 Oct, 12:00 UTC

—

✅ Pact Quest #5 is closed! Thank you all.

The answer was typeof-principal. A Kadena account name can be a "principal", and its prefix says which kind of guard controls it: k: a single public key, w: a multi-key keyset, u: a user guard, c: a capability guard. typeof-principal returns that prefix.

Its neighbours, easy to mix up:
• is-principal — only checks the name is shaped like a principal
• validate-principal — proves a name really belongs to a guard you hold
• create-principal — builds the name from a guard
📖 kda-chain.org/docs/pact-5/gu…

Questions: t.me/PactCommunityO…

#Pact #Kadena #KadenaCommunityEdition #KadenaCE kadena:native

🟢 Pact Quest #5 is open.

Which Pact builtin tells you which kind of guard an account name's prefix stands for? (name only, lowercase)

Claim → pact-community.org/token, select quest-5
100 PCO · one per account · until Fri 9 Oct, 12:00 UTC
📖 kda-chain.org/docs/smart-con…

#kadena $KDA #PCO #SmartContracts

🧭 Pact Quest #5 opens Saturday at 14:00 UTC — accounts, guards and principals.

A Kadena account name can be a "principal" — the name itself encodes the guard that controls it, starting with a prefix like k: or r:. Which builtin returns which kind of guard that prefix stands for?

(lowercase, hyphenated, exactly as you would write it in Pact — the name only, no parentheses)

The answer is one page away in the Kadena CE docs:
📖 kda-chain.org/docs/smart-con…
📖 kda-chain.org/docs/pact-5/gu…

Claim from 14:00 UTC → pact-community.org/token, select quest-5
100 PCO · one claim per account · closes Fri 9 Oct, 12:00 UTC

—

✅ Pact Quest #4 is closed — Thank you all.

The answer was with-capability. It grants a capability for exactly one block of code: the capability's own checks run when it is acquired, inside the block the permission holds, and when the block ends it is gone. PCO's own transfer works this way — tokens move only inside the block that holds TRANSFER.

The three it is easily confused with:
• require-capability — checks one is held, grants nothing
• compose-capability — grants one from inside another capability's definition
• install-capability — pre-authorises a managed capability
📖 kda-chain.org/docs/pact-5/ca…

Questions: t.me/PactCommunityO…

#Pact #Kadena $KDA