MASL is a CBOR-based metadata system that is designed to work well with content-addressed and decentralised systems, to enable fully self-contained, self-certified content distribution.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
DASL: RASL — Retrieval of Arbitrary Structures & Links
RASL is a URL scheme used to identify content-addressed DASL resources along with a simple HTTP-based retrieval method.
DASL: DRISL — Deterministic Representation for Interoperable Structures & Links
DRISL is a serialization format that is deterministic (so that the same data will have the same CID) and that features native support for using CIDs as links. It is based on CBOR, using a narrow profile of CBOR's "Core" featureset called "[[cborc-42]]", specified formally in this IETF document.
DASL: Content-Addressable aRchives (CAR)
The CAR format offers a serialized representation of set of content-addressed resources in one single concatenated stream, alongside a header that describes that content.
DASL: Governance of the DASL Project
The goal of the DASL Project is to develop content-addressing primitives and the technologies that build on them, with a view towards enabling unbundled software and protocol architectures that best align with and promote democratic systems.
DASL: ATFISL — Content Discovery with the AT Protocol
ATFISL is a content discovery system for CIDs built with the AT Protocol. Publishers announce download locations for CIDs by publishing records to their AT Protocol repositories. Indexers aggregate these records into a lookup table from CIDs to live locations. ATFISL is complemented by FISL which defines an HTTP query API for ATFISL records.
@dasl/weasl - npmx
Warehouse that's Extensible for Arbitrary Structures & Links (WEASL) — @dasl/weasl — DASL store
DASL: FISL — Finding Internet Structures & Links
FISL is an HTTP lookup API that maps CIDs to locations, so that a client with a CID can find out where to retrieve it from and who announced it. A client sends a CID, and the index returns the URLs where content can be retrieved, along with the identity of the publisher when known. FISL specifies only the query interface, so it works with any indexing system that supplies location records.
DASL: MUXL — Media Uniform eXact Layout
MUXL is a deterministic and highly-restrictive subset of ISO-BMFF, enabling stable content-addressed identifiers for video and audio. It's like DRISL for MP4 files!
DASL: Tiles Protocols
Tiles ([[tiles]]) are intended for use in a diversity of environements. Depending on the environment that they find themselves embedded in, they will have access to different capabilities that expose various features and communicate with the host environment. Tiles Protocols are the mechanisms through which these integrations are made available.
DASL: Web Tiles
Tiles are composable web docs and apps that can safely be used in arbitrary contexts and assembled from multiple sources to carry out complex user interface tasks. Their composability, security, and privacy properties make them ideal for use in social media, chat, agents, and malleable software.
Just Enough Governance: Introducing Steward Governance for DASL
When we started working on DASL, it was little more than an experiment. We talked to as many people as we could who had been interested in content addressing but couldn't make it work for their needs. The result was radically focused on interoperability and adoption, on a mission
STAR: ordered key-value archive format #21
Hello! I'd like to propose new work for DASL: the [STAR](https://tangled.org/microcosm.blue/star/tree/main/v1-star) (/STAR-lite) archive format. I originally made STAR as a stricter, simpler, safer, more efficient alternative to CARs for atproto public repository exports. Its v0 now has several library implementations and has at least two production producers and half a dozen consumers in the Atmosphere, but is very atproto-coupled. STAR is [being considered](https://github.com/bluesky-social/proposals/pull/114) as the standard format for [atproto spaces](https://github.com/bluesky-social/proposals/tree/main/0016-permissioned-data) repo exports. After iteration with @dholms.at and @bnewbold.net, STAR's spaces-compatible v1 is becoming a more general-purpose format for ordered key-value data, and I think, a potentially good fit with DASL. Following the DASL governance [steps for proposing new work](https://dasl.ing/governance.html#:~:text=Proposing%20New%20Work): ## What will be implemented A specification ([in progress](https://tangled.org/microcosm.blue/star/tree/main/v1-star)), reference implementations, test vectors. ## Who wants it Data exports in atproto is one established use-case. People have been motivated to request public archives in STAR-lite format from [hubble](https://web.hubble.microcosm.blue/): 260M STAR-lite archives served vs 6M CAR. Repositories compress to a bit under half the size compared to CARs, which translates directly into faster network backfill rate in many cases (this is not exactly apples-to-apples: STAR-lite omits the MST entirely since it's deterministic from the data and cheap to reconstruct). More on the pain it addresses [here](https://pckt.blog/b/data-service-diaries/war-on-cars-5xa5v73). The atproto spaces protocol proposes an LtHash set as its canonical data integrity structure instead of a MST: flat key-value with no tree or DAG structure at all to benefit from CAR's CID indexing, fitting more naturally (and without the incompressible CID overhead) into something like STAR. ## Fit with existing primitives STAR-lite builds on DRISL/DASL-CBOR, and uses `varint`-prefixed framing like DASL-CAR. Where DASL-CAR fits DAG-shaped data well, STAR-lite is a more natural fit for flat key-value data. ## Confirm willingness to serve as an editor I confirm! ## Other criteria not covered above Implementation: there is currently a v0 reference [rust](https://crates.io/crates/star-lite) + a third-party Objective-C implementation. I will be adding v1 support to the rust library soon. I think there will be more implementations, especially if it gets adopted by atproto spaces. Community Support: Existing growing uptake of the v0 format, possible standardized use in atproto-spaces, [active evolution](https://bsky.app/profile/bad-example.com/post/3mwc5n4f4gk24) based on feedback. --- Atmosphere post: https://bsky.app/profile/did:plc:lulmyldiq4sb2ikags5sfb25/post/3mwohvqxhpc2h Upcoming CID Congress presentation at https://luma.com/8w8swmx2
veritiles v0.3 is out 🚀 The proof format is now DASL + AT Protocol compatible from the ground up, using raw/dag-CBOR CIDs, DRISL descriptors and MASL bundles. github.com/guillaumemichel/veritiles @dasl.ing @atproto.com
GitHub - guillaumemichel/veritiles: Verified map tiles: fetch PMTiles byte ranges from any untrusted HTTP host and cryptographically verify every byte against a content identifier before your map renders it. Zero dependencies; drop-in pmtiles Source for MapLibre GL, Leaflet, and OpenLayers.
github.com