Verify session: Native Tokens Resources (Q1 2026, 08-open-clinic-1 resources)

Aperta
#352 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, markdown, python, shell

Direzione di ricerca

Start with website/docs/working-group/sessions/q1-2026/08-open-clinic-1/session-1/session-resources/readme.md, then run its commands in a clean directory exactly in order. Check every referenced package, image tag, version, and link, recording exact failures and any required correction. The work is done when every check in #301 can be ticked and findings are posted here.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation pinned

Part of the tutorial verification checklist in #301.

Page: website/docs/working-group/sessions/q1-2026/08-open-clinic-1/session-1/session-resources/readme.md
Title on the site: Native Tokens Resources
Section: Q1 2026, 08-open-clinic-1 resources

How to follow along
  1. Open the page on the site and read it end to end before running anything.
  2. Work through it in a clean directory, as a new user. Do not skip setup steps because you already have the tooling; the point is to see what a newcomer sees.
  3. Run every command exactly as written, then compare the output with what the page claims it should be.
  4. Open every link, including links inside code comments and references.

Done when

  • Every command runs as written, or the page is updated so that it does
  • Every link resolves
  • Every package, image tag and version referenced still exists
  • The matching box in #301 is ticked and the findings are posted here
What to record when a step breaks
  • The exact command and the error text, copied rather than summarised
  • The heading or step number it sits under
  • What you changed to make it work

Commands the page asks you to run, in order:

# 1. Install cardano-node (includes CLI)
# See: https://docs.cardano.org/getting-started/installing-the-cardano-node

# 2. Generate policy keys
cardano-cli address key-gen \
  --verification-key-file policy.vkey \
  --signing-key-file policy.skey

# 3. Create simple policy
echo '{"type":"sig","keyHash":"'$(cardano-cli address key-hash --payment-verification-key-file policy.vkey)'"}' > policy.json

# 4. Get policy ID
npm install lucid-cardano
npm install @martifylabs/mesh
pip install pycardano
# 1. Query UTXOs via Blockfrost
curl "https://cardano-preview.blockfrost.io/api/v0/addresses/addr1.../utxos" \
  -H "project_id: YOUR_API_KEY"

# 2. Build transaction with CLI
cardano-cli transaction build --tx-in ...

# 3. Submit via Blockfrost
curl -X POST "https://cardano-preview.blockfrost.io/api/v0/tx/submit" \
  -H "project_id: YOUR_API_KEY" \
  -H "Content-Type: application/cbor" \
  --data-binary @tx.signed
Lingua principale
TypeScript
Stelle
13
Fork
24
Merge medio
2g 3h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IntersectMBO/developer-experience

Tutte le issue di IntersectMBO/developer-experience

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.