Yes. Watch Kaspa Covenant Dev Workshop - KCC20 & Argent, published on 9 September 2026 on Kaspa Native. It covers why a token convention is needed, writes a token actor in Argent, and works through building a transaction. [1][2][3]
What the workshop teaches
The workshop connects the token rules to actual code. These are useful places to start:
- [19:42: Why KCC-20 exists](https://www.youtube.com/watch?v=vZUS45fY6sk&t=1182s). The presenter explains why tokens need shared rules so other programs can recognise and use them. KCC-1 and KCC-2 provide common ways to call programs and represent ownership. KCC-20 uses those foundations for fungible tokens, meaning units that are interchangeable with one another. [1]
- [23:10: Receiving tokens through borrowing](https://www.youtube.com/watch?v=vZUS45fY6sk&t=1390s). Creating a new token coin also requires KAS in that coin. The presenter explains an alternative: add tokens to a recipient’s existing token coin instead of creating another one. [4]
- [33:00: Writing the token state](https://www.youtube.com/watch?v=vZUS45fY6sk&t=1980s). The coding starts with the data each token coin carries: its token amount, owner, ownership scheme, borrowing settings and extension commitment. An actor is then defined to guard that state. [2]
- [40:26: Actors and applications](https://www.youtube.com/watch?v=vZUS45fY6sk&t=2426s). A chess application illustrates how several actors can belong to one application while holding different kinds of state. The token example introduces separate transfer and transfer-delegation paths. [5]
- [1:12:30: Leader and delegator](https://www.youtube.com/watch?v=vZUS45fY6sk&t=4350s). One input performs the shared checks. Other inputs can rely on it after verifying the required relationship, rather than repeating all the work. [6]
- [1:23:20: Binding checks to real outputs](https://www.youtube.com/watch?v=vZUS45fY6sk&t=5000s). The presenter explains why declared token states must match the transaction’s actual outputs, then demonstrates compilation and handles compiler errors. [7]
- [1:53:08: Transaction construction](https://www.youtube.com/watch?v=vZUS45fY6sk&t=6788s). The demonstration assembles actor inputs and outputs, supplies covenant bindings, and works through Rust type errors. [3]
How to use the recording today
Treat it as a worked design lesson, not a promise that every line can be copied unchanged. On 29 September 2026, IzioDev announced a breaking Argent import change: import actor Foo from "..."; was no longer supported. The alternatives were a non-namespaced import or import "..." as FooModule. [8]
The standard also progressed after filming: Manyfest announced KCC-20’s move to Last Call, its final-review stage, on 7 October 2026. That announcement was not a declaration of final status. [9]
For the central safety lesson, watch [1:23:20](https://www.youtube.com/watch?v=vZUS45fY6sk&t=5000s): checking supplied data is not enough unless the contract also binds it to the transaction’s real outputs. [7]