jim-toth

---

GroupId: "SWS-5" Title: "Following Interface" Description: "This document describes the standard interface for SmartWeave Contracts that represent a list for the tracking of unique blockchain addresses (i.e. "following")." Topics:

• "specs"
• "standard"
• "sws"
• "smartweave"
• "following"

jim-toth

SWS-4: Multi-Token Standard Interface

Status: Draft

Version: 1.0.0

Author: Jim Toth (jim@artby.city)

Abstract

This document describes the standard interface for SmartWeave Contracts that represent multitple tokenized assets simultaneously.

jim-toth

SWS-2: SmartWeave Token

Status: Published

Version: 1.1.0

Abstract

This document describes the standard interface for tokenized asset SmartWeave Contracts. The SmartWeave Token Spec refers to a SmartWeave Contract that can grant ownership properties to any arweave asset when it is deployed, effectively

jim-toth

SWS-3 Multi-Token Standard

Token Interface

totalSupply() => { totalSupply: number }

balanceOf(address: string) => { address: string, balance: number }

transfer(to: string, amount: number) => void

jim-toth

Filename: 101-relay-operator-alternate-identity.md
Title: Broadcasting Relay Operator Alternate Identities
Author: Jim Toth - jim@memeticblock.io, Slava Mushyaokv - slava@memeticblock.io, & ATOR Labs LLC
Created: 2023-07-18
Status: Draft

Overview

jim-toth

---

GroupId: ANS-113

Title: "Related Assets"

Description: "This document describes the Related Asset specification for association of assets with a primary asset through tags."

Topics:

• specs, standard, assets, related, related assets, related-to, preview, thumbnail

jim-toth

Arweave Related Assets (Preview / Thumbnail) Spec

Abstract

As the permaweb grows in popularity, complexity, and use there has been a growing need to associate assets as related to a logical asset, work, or publication. One major pain point for many permaweb builders is the large size of data assets. For example, a photographer may wish to publish a high-definition photograph ranging in size from hundreds of megabytes to one or more gigabytes. Another example would be video or 3D model assets that would tax the end user's browser when consuming these assets through aggregation dapps. A standard specification is thus proposed as a way to enhance composability and consumption of assets across the permaweb.

Use Cases

1. Thumbnail/preview asset association to represent primary assets

• Example: A photographer wants to associate smaller, web-friendly versions of large photographs

jim-toth

type LengthOfString<
  S extends string,
  Acc extends 0[] = []
> = S extends `${string}${infer Rest}`
  ? LengthOfString<Rest, [...Acc, 0]>
  : Acc['length']

export type HexNumbers =
  | '0'
  | '1'

jim-toth

Arweaver's Art By City Protocol Summary & ANS-110 Discussion

History

Art By City started primarily as an artist-focused DApp (https://artby.city) during the Open Web Foundry in Q4 2021. As our focus is on utilizing a decentralized web to empower creators through discoverability and curation, we quickly realized the need to categorize different types of creative asset publications, their intended rendering containers, metadata, licensing, and associated meta-actions such as liking, tipping, or sharing. We began outlining a specification to be implemented as tags on Arweave transactions so that our own dapp could discover these assets, know how to render them properly, display the associated creator metadata (e.g. title, description, license), and begin building a curation graph we could crawl later through likes and tips. This work was designed while the DApp was being developed by necessity and through code.

We continued to refine the spec, through code and many conversations - we've spoken to dozen

jim-toth

Keybase proof

I hereby claim:

• I am jim-toth on github.
• I am jimtoth (https://keybase.io/jimtoth) on keybase.
• I have a public key ASA-y8vlOw2yuczxegCGepIQU6ZrhQTSMPfPg2v8gjXflAo

To claim this, I am signing this object: