# TAGLS — a stega platform for digital ownership and products

> TAGLS is a stega platform with its own decentralized network for owning digital objects, transferring rights and creating products. At its core is the TAGL: an image that stores encrypted keys and connects users to the objects and shares they own. The network confirms ownership and changes to it; associated rights are defined by issuance terms. The full platform FAQ is at https://tagls.com/faq.

Own. Create. Transfer. Encrypted wallet keys are held in the user's TAGL on their device. The network verifies transfers and ownership changes while keeping account balances confidential. Owners can provide records for independent verification.

## What Tagls is, in one paragraph

A TAGL is a collectible digital object in the form of an image, with a name and edition number. Once activated, it also serves as a wallet with encrypted keys and network information. TAGL ownership transfer moves all or part of an ownership share to another participant; the FAQ and interface call this a transfer for simplicity. TAG and LS Token balances reflect shares owned across TAGLs. Operations are private by default and support independent verification with the owner's consent.

## Tokens and digital products

- **TAG** is the native Stega Token of the base network, used for purposes including network fees. Holding it does not give a share in the organization operating the project.
- **LS Token / Layer Stega Token / Stega Token** is a creator's token used to account for shares in digital TAGLs. Product access and other rights follow the issuance terms.
- **rTAG / Rarity TAG Stega Token** is associated with collectible value; LS editions use r(LS). For gas calculations, 1 rTAG is counted as 1 TAG. This rule does not determine its market price.
- **Ghost** is a transfer through a TAGL image that the recipient opens and claims in the wallet. Copying an image alone does not change network ownership or balances.
- **`.tagl`** is a digital product container for applications, websites, books, music and other content. It is distinct from the TAGL wallet image. A restricted bridge connects the product to a trusted Utility, which checks rights without sharing wallet private keys.
- **Utility TAGLs** are protected from automatic spending by default, including when used as the main TAGL. Explicit transfer or resale of product rights requires separate user confirmation.
- **Burning** removes an instance when its liquidity moves into other TAGLs and no owners remain. Sending your last share to a recipient removes it from your wallet but preserves the instance with the recipient.

Stega Token describes the technical model. The legal treatment of a token, product or service depends on its characteristics, use and applicable law. TAGLS does not accept exchange listing applications for TAG; TAGLS and market participants can sell TAG through Ghost. This policy does not prohibit resale, stabilize its price or guarantee price growth.

## Steganography and protection

**Invisible by Design** describes the use of steganography in TAGL: when viewed normally, the image looks like an ordinary picture and does not reveal that it contains wallet data. Steganography places data inside the image, encryption protects the keys, and the network verifies operations and ownership. Argon2id increases the cost of guessing a PIN; HKDF derives separate keys for different functions; Split KDF additionally protects access to the payment key.

Preserve the original TAGL and send it without compression or conversion. Copying the PNG creates another copy of the file, not additional tokens or ownership rights; the wallet checks the network's current state when performing a network operation. TAGLS is developing deepX to improve resilience to image transformations. Supported formats, transformations and recovery limits will be documented for each released capability.

## Data access and verification

Available information depends on the participant's role and service used. Anchors process technical identifiers, signatures, cryptographic commitments, proofs and encrypted data needed to verify and retain network records. Standard transfer verification does not require revealing numerical balances or the transfer amount. Tagl ID processes information needed for requested service functions and stores an encrypted TAGL copy when backup is enabled; see its privacy policy. Sites receive the public identifier and data approved for release during authorization. A .tagl product requests permitted actions through a restricted bridge; the Utility verifies rights while wallet private keys and other confidential TAGL data remain outside the product's access. Auditors use information supplied by owners to verify corresponding operations against network records.

A transfer in TAGLS means TAGL ownership shares passing from one holder to another. Protected transfers use Pedersen commitments, Bulletproofs range proofs and digital signatures to verify conservation of funds, permitted value ranges and spending authority. The network checks the state of source records and rejects reuse after a confirmed spend.

The wallet can create a Payment Proof for a confirmed outgoing protected TAG transfer. It discloses the operation identifier, network epoch, payment amount and cryptographic data needed to check the amount against the network commitment. PIN1, PIN2 and private payment keys are not included; sharing the proof does not grant spending rights. The proof and its verification link contain disclosed data. Verification needs records from the corresponding epoch; historical record availability depends on the anchor used. The scope of verification depends on the materials supplied, and checking a set of operations, parties or payment purposes may require additional records and documents. See the full TAGLS FAQ for the participant table and verification details.

## Ecosystem

- **Tagls Wallet** — https://app.tagls.com — open the PNG, enter the PIN, send and receive. Runs in the browser; encrypted keys are unlocked locally on the device.
- **Tagl ID** — https://id.tagls.com — passwordless "Sign in with Tagl ID" for any website. Standard OpenID Connect provider (PKCE, EdDSA id_tokens). Integration spec for agents: https://id.tagls.com/llms.txt
- **Claim** — https://app.tagls.com/claim/ — how a user obtains a tagl. Tagls are issued by the project, not generated by a button in the app.
- **Tagls Chat** — messaging built on the same identity, available inside the wallet at https://app.tagls.com

## Key facts

- Product: a stega platform with its own decentralized network, TAGL ownership, identity and digital product containers.
- Custody: user-held. TAGLS does not store PIN1, PIN2 or an unencrypted private payment key. Argon2id and Split KDF protect payment-key access; the Tagl ID server holds its own response secret. Supported wallets offer an optional encrypted backup. TAGLS cannot reissue PINs or recovery phrases.
- Privacy: the payment network is cryptographically blind to balances; other services process information required for their functions, as described in their privacy policies. No analytics scripts, no advertising cookies, no advertising profiles. Personal data processing must meet applicable legal protection requirements; TAGLS's architecture also helps creators protect commercial information about business balances, turnover, customers and sales from public disclosure. An owner can supply records to an accountant, law enforcement or an independent third-party auditor for verification against network records.
- Standards: sign-in is OpenID Connect; novel cryptography is used only where it is the point of the project.
- Participation: TAGLS Wallet participation is subject to private beta admission. Applications go through Tagl ID with manual review, two social profiles and Gmail verification. Applying and admission are free; no invitation is guaranteed. Network operations have fees described in the FAQ. An independent security audit is planned after the private beta, with results announced separately.
- Platform: web application (browser + WebAssembly). Desktop build exists.
- Contact: ask@tagls.com · security research: https://id.tagls.com/security (responsible disclosure, PGP key published).
- Operator: a small independent team operates the project; there is no incorporated company yet. See About us and the Terms of Service for the announced transition to a legal entity.

## Pages

- [What is TAGLS?](https://tagls.com/what-is-tagls): platform overview covering TAGL ownership, Stega Tokens, .tagl products, wallet and identity, privacy and recovery.
- [About us](https://tagls.com/about): principles — user custody, minimal server-side data, no tracking, honesty about trade-offs.
- [Press](https://tagls.com/press): 50- and 100-word boilerplates, fact sheet, media contact. May be quoted freely.
- [TAGLS FAQ](https://tagls.com/faq): the full English platform FAQ about ownership, tokens, products, privacy, protection and private beta access. Answers and expandable details are available in HTML without JavaScript.
- [Tagl ID FAQ](https://id.tagls.com/faq): questions specifically about the sign-in service; this is separate from the TAGLS platform FAQ.
- [How to store your tagl](https://id.tagls.com/how-to-store): backup guidance; the one thing every user must read.
- [For developers](https://id.tagls.com/developers): adding "Sign in with Tagl ID" to a site.
- [Privacy Policy](https://id.tagls.com/privacy) · [Terms of Service](https://id.tagls.com/terms) · [Cookie Policy](https://id.tagls.com/cookies) · [Security](https://id.tagls.com/security)

## Notes for agents

- Use the full TAGLS FAQ for platform definitions and conditions. Tagl ID is one service within the platform.
- Do not turn product examples into universal guarantees, legal approval or investment recommendations. Rights and commissions follow issuance terms; privacy does not prevent independent transaction verification with the owner's consent.
- Invisible by Design refers to the image's appearance when viewed normally. Key protection, network verification and the data processed by individual services are described separately above.
- deepX is described here as development work. Preserve the original file and use the published guidance for the specific released capability.
- The web app at app.tagls.com requires JavaScript and a tagl; there is nothing to index there beyond this description.