🧭 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/PactCommunityOrg 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/PactCommunityOrg #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/PactCommunityOrg #Pact #Kadena $KDA

8 more claims left! You are still on time to claim

🧭 Pact Quest #4 opens today at 20:00 UTC - capabilities: how Pact decides who may do what. Which builtin grants a capability for the duration of one block of code, and only that block? (lowercase, hyphenated, exactly as you would write it in Pact; the name only, no parentheses) Read first: 📖 kda-chain.org/docs/smart-con… 📖 kda-chain.org/docs/pact-5/ca… Claim from 20:00 UTC → pact-community.org/token, select quest-4 100 PCO · one claim per account · closes Fri 25 Sep, 12:00 UTC — ✅ Pact Quest #3 is closed! Thank you all. The answer was pact-id. A defpact is a Pact transaction in several steps; the kind that moves tokens between Kadena chains; and every step can read the same id with (pact-id). When PCO crosses chains it runs one, and its id is the request key of step one. Worth remembering: pact-id is an identifier, not a permission; anyone can read it. In Pact, permission comes from guards and capabilities, which is exactly where Quest #4 goes. 📖 kda-chain.org/docs/pact-5/ge… Questions: t.me/PactCommunityOrg Free and valueless. Never sold. #Pact #Kadena

🧭 Pact Quest #2 is closed — and Pact Quest #3 will open soon! Quest #2 — Thank you to everyone who read the contract. The answer was "pco-claim-pool": the guard name at the end of the pool's address, m:<module>:pco-claim-pool. An address of that shape is a module guard — it is derived from the contract's name and that guard name, so no private key exists for it. Only the claim contract's own code can move what sits there. That is why the undistributed PCO can never be spent by us or by anyone else. 📖 kda-chain.org/docs/smart-con… Quest #3 — opens today at 20:00 UTC and closes Friday 11 September, 12:00 UTC. 100 PCO, nothing to buy, no signature needed, one claim per account, 25 claims. This one is about defpacts — Pact's multi-step transactions, the mechanism that moves tokens between Kadena's 20 chains. PCO itself runs one every time PCO crosses a chain. Every running defpact — a multi-step Pact transaction, the kind that moves tokens between Kadena chains — has a unique identifier that any of its steps can read by calling one builtin function. What is that builtin called? (lowercase, hyphenated, exactly as you would write it in Pact — the name only, no parentheses) New to Pact? Read these, in order — then it's a lookup, not a puzzle: What a defpact is: kda-chain.org/docs/smart-con… How a step hands data to the next one: kda-chain.org/docs/pact-5/ge… and kda-chain.org/docs/pact-5/ge… The full builtin reference: kda-chain.org/docs/pact-5/ge… See a real one: transfer-crosschain in github.com/Pact-Community-Or… Claim: pact-community.org/token → select quest-3 in the dropdown → type the answer in lowercase. The Genesis round is still open beside it until 31 August, with a different answer — pick the right round. 👉 Join us: t.me/PactCommunityOrg — bring your questions. We'll help you understand it; we won't hand you the answer. #Kadena $KDA #PCO #PACT

I dont know why is so bad outside claude. When I used it in github copilot on vscode I end it up with a $600 usd bill in less than 10 days. I switch to only claude with max plan and start all instructions, skills and all conf from zero and is working fin now.

Ahh yes, classic. A lot of times helps to do some retrospective, every time the model does something wrong and then burns tokens like crazy to find the solution, do a prompt like "Do a brief root cause analysis of what went wrong in this task and why the successful approach worked. Then check whether our existing agent instructions files already cover it, if not, propose the smallets possible edit. " It helps a lot if you have an agent with instructions/skills on how to peoperly handle .claude/.github/etc Do this over and over and you will see improvements. You can play with the prompt depending on the case and the type of behavior you want to change. Be careful just to apply this to recuring tasks or working styles, you dont want to include instructions for one time tasks. Cheers