Checking connection…
Skip to sign-in and submission

Agentic Coding on Cardano

Earn a credential that is proof of what you learned

  1. I can direct an AI coding agent, grounded in pinned documentation, to build, sign and submit Cardano transactions from a wallet I control.
  2. I can predict a transaction's fee before submitting it and confirm it matches the on-chain fee to the lovelace.
  3. I can register a stake key and delegate to a stake pool while my ada stays spendable.
  4. I can mint a native asset under a native-script policy without deploying a token contract.
  5. I can deploy a validator I specified and audited, then lock and unlock funds with it.
  6. I can chain dependent transactions and submit parallel transactions without waiting for confirmations.
  7. I can take part in on-chain governance by delegating my voting power, or by registering as a DRep and voting.
  8. I can ship a dApp in which a CIP-30 browser wallet signs a transaction the dApp builds.
  9. I can write a validator that checks a token through a reference input without spending it.

The credential lives on the Cardano blockchain, and it is yours to keep. In this course, you completed exercises on Cardano Preprod. This credential is on Cardano Mainnet.

Your assignment: submit your trails.md

Since Unit 8, your agent has added a line to trails.md after every on-chain action. That file is your course record, and it is your final assignment. Paste the whole of it on this page.

A Cardano Academy reviewer checks the transactions in it on Cardano's preprod network. When they accept it, you claim your credential on this page.

What your record contains

It opens with one line: Course wallet: addr_test1…. Every transaction below it was made by that wallet, unless a step says otherwise.

Below the header there is one line per transaction, in the order you made them. Each line gives the unit, what you did, the prompt you gave your agent, the transaction id and the fee.

The reviewer looks for this evidence, one item for each learning target above, in the same order:

  1. Every transaction comes from the wallet in the header, with the prompt that produced it.
  2. Your Byron transactions, with the fee you predicted beside the fee on-chain.
  3. One transaction carrying the registration and delegation certificates, then a spend from the same wallet.
  4. Your mint transaction and its policy id. The same asset appears in every later stamp.
  5. Your lock and unlock transactions. The script hash in your Goguen-II stamp matches the script address.
  6. Three chained transactions, then a fan-out to five UTxOs and five parallel spends. Include the rejection message from your double-spend contest.
  7. Your vote-delegation transaction, or your DRep registration and your vote.
  8. Your Agentic-Era stamp, sent from your browser wallet to the course wallet.
  9. Your token-gate unlock, with the token UTxO as an unspent reference input.

Your seven era stamps come last (BYRON, SHELLEY, GOGUEN1, GOGUEN2, BASHO, VOLTAIRE and AGENTIC), with the Era Gathering transaction that spends them all.

Before you submit

Tidy your record. Prompt your agent:

"Format trails.md into its final form: one line per transaction in the order I made them, each with the unit, what it was, the prompt, the transaction id and the fee, and the gathering transaction last."

Read it top to bottom. Check that the header is the wallet you used and that all seven stamps are there.

Paste trails.md only. Never paste your mnemonic, or anything from your .env file.

How it's reviewed

A reviewer reads your record and checks the transactions on preprod. They accept it, or send it back with a note. If it comes back, revise it here and submit it again.

Agentic Coding on Cardano

Your assignment: submit your trails.md

Since Unit 8, your agent has added a line to trails.md after every on-chain action. That file is your course record, and it is your final assignment. Paste the whole of it on this page.

A Cardano Academy reviewer checks the transactions in it on Cardano's preprod network. When they accept it, you claim your credential on this page.

What your record contains

It opens with one line: Course wallet: addr_test1…. Every transaction below it was made by that wallet, unless a step says otherwise.

Below the header there is one line per transaction, in the order you made them. Each line gives the unit, what you did, the prompt you gave your agent, the transaction id and the fee.

The reviewer looks for this evidence, one item for each learning target above, in the same order:

  1. Every transaction comes from the wallet in the header, with the prompt that produced it.
  2. Your Byron transactions, with the fee you predicted beside the fee on-chain.
  3. One transaction carrying the registration and delegation certificates, then a spend from the same wallet.
  4. Your mint transaction and its policy id. The same asset appears in every later stamp.
  5. Your lock and unlock transactions. The script hash in your Goguen-II stamp matches the script address.
  6. Three chained transactions, then a fan-out to five UTxOs and five parallel spends. Include the rejection message from your double-spend contest.
  7. Your vote-delegation transaction, or your DRep registration and your vote.
  8. Your Agentic-Era stamp, sent from your browser wallet to the course wallet.
  9. Your token-gate unlock, with the token UTxO as an unspent reference input.

Your seven era stamps come last (BYRON, SHELLEY, GOGUEN1, GOGUEN2, BASHO, VOLTAIRE and AGENTIC), with the Era Gathering transaction that spends them all.

Before you submit

Tidy your record. Prompt your agent:

"Format trails.md into its final form: one line per transaction in the order I made them, each with the unit, what it was, the prompt, the transaction id and the fee, and the gathering transaction last."

Read it top to bottom. Check that the header is the wallet you used and that all seven stamps are there.

Paste trails.md only. Never paste your mnemonic, or anything from your .env file.

How it's reviewed

A reviewer reads your record and checks the transactions on preprod. They accept it, or send it back with a note. If it comes back, revise it here and submit it again.