Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .clabot
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
{
"contributors": [
"expede",
"MichaelMure"
"MichaelMure",
"alanshaw"
]
}
8 changes: 8 additions & 0 deletions Notices.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,14 @@ Specification version: 0.0.0 or later

---------------------------------------------------------------------------------

Licensee’s name: Alan Shaw

Authorized individual and system identifier: alanshaw

Specification version: 0.0.0 or later

---------------------------------------------------------------------------------

## Withdrawals

Name of party withdrawing:
Expand Down
9 changes: 4 additions & 5 deletions Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The UCAN spec itself is transport agnostic. This specification describes how to

UCAN tokens, regardless of their kind ([Delegation], [Invocation], [Revocation], [Promise]) MUST be first signed and serialized into DAG-CBOR bytes according to their respective specification. As the token's CID is not part of the serialized container, any CID returned by this operation is to be ignored.

All the tokens' bytes MUST be assembled in a [CBOR] array. The ordering of tokens in the array MUST NOT matter. This array SHOULD NOT have duplicate entries.
All the tokens' bytes MUST be assembled in a [CBOR] array. The ordering of tokens in the array MUST NOT matter. This array SHOULD NOT have duplicate entries and MUST be ordered bytewise to ensure a deterministic encoding.

That array is then inserted as the value under the `ctn-v1` string key, in a CBOR map. There MUST NOT be other keys.

Expand Down Expand Up @@ -87,22 +87,21 @@ While it is tempting to write a single implementation to read and write a contai

# 5 Acknowledgments

Many thanks to all the [Fission] team and in particular to [Brooklyn Zelenka] for creating and pushing [UCAN] and other critical pieces like [WNFS], and generally being awesome and supportive people.
Many thanks to all the Fission team and in particular to [Brooklyn Zelenka] for creating and pushing [UCAN] and other critical pieces like [WNFS], and generally being awesome and supportive people.

<!-- External Links -->

[BCP 14]: https://www.rfc-editor.org/info/bcp14
[Brooklyn Zelenka]: https://github.com/expede
[CBOR]: https://www.rfc-editor.org/rfc/rfc8949.html
[Consensys]: https://consensys.io/
[Delegation]: https://github.com/ucan-wg/delegation/tree/v1_ipld
[Fission]: https://fission.codes
[Delegation]: https://github.com/ucan-wg/delegation
[GZIP]: https://datatracker.ietf.org/doc/html/rfc1952
[Hugo Dias]: https://github.com/hugomrdias
[Invocation]: https://github.com/ucan-wg/invocation
[Michael Muré]: https://github.com/MichaelMure/
[Promise]: https://github.com/ucan-wg/promise/tree/v1-rc1
[Revocation]: https://github.com/ucan-wg/revocation/tree/first-draft
[Revocation]: https://github.com/ucan-wg/revocation
[UCAN]: https://github.com/ucan-wg/spec
[WNFS]: https://github.com/wnfs-wg
[cache poisoning]: https://en.wikipedia.org/wiki/Cache_poisoning
Expand Down