TAGLS FAQ

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; the rights associated with an object are defined by its issuance terms.

TAGLS puts this model of digital ownership into a familiar wallet. Users receive and send Stega Tokens, use digital products, and can transfer or resell rights to them under their issuance terms.

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.

More about the platform

Creators can issue collectibles, digital asset passports, tickets and access rights to their products. The .tagl format lets them package applications, books, music and other content with defined terms of use.

Users manage objects through TAGLS Wallet and use Tagl ID to sign in to services and confirm information.

TAG and LS Token balances reflect the shares in TAGLs owned by the user. Transactions are private by default and support independent verification with the owner's consent.

Personal data processing must meet the applicable legal requirements for its protection. TAGLS's architecture also helps product creators protect commercial information about their business balances, turnover, customers and sales from public disclosure.

Operations remain verifiable: a wallet owner can provide an accountant, law enforcement or an independent third-party auditor with the information needed to check their operations against the network's records. Privacy and independent verification are both part of TAGLS's architecture.

The information available depends on the participant's role and the service used. Account balance confidentiality works alongside processing the data needed to confirm operations, authorize access and provide services.

Participant	Available information
Wallet owner	After unlocking the wallet, can access their balances, shares and operation history.
Network anchor	Processes technical identifiers, signatures, cryptographic commitments, proofs and encrypted data needed to verify and retain network records. Standard transfer verification does not require it to reveal the numerical values of balances or the transfer amount.
Tagl ID	Processes information needed for authorization and the service functions requested. When backup is enabled, stores an encrypted copy of the TAGL. The privacy policy describes the data processed.
A site using Tagl ID	Receives the user's public identifier and the data the user approved for release during authorization.
A product in a .tagl container	Requests permitted actions through a restricted bridge. The Utility verifies the user's rights and permits the corresponding actions. The wallet's private keys and other confidential data stored in the TAGL remain outside the product's access.
Auditor	Receives information supplied by the owner and uses it to verify the corresponding operations against network records.

Public edition descriptions, product terms and information users disclose themselves have their own access rules.

TAGL ownership transfer means moving an ownership share in a TAGL from one participant to another. You can transfer all or part of the share you own. For simplicity and familiarity, this FAQ and the TAGLS interface call this operation a transfer.

The network confirms the ownership change, and the wallet reflects it in shares and TAG or LS Token balances. Additional rights associated with a share, such as access to a product or permission to use an image, are defined by the issuance terms.

The wallet generates cryptographic data that lets the anchor verify an operation without receiving balances or the transfer amount in plaintext.

A transfer in TAGLS means TAGL ownership shares passing from one holder to another. Protected transfers in TAGLS use Pedersen commitments: they bind hidden numerical values to verifiable cryptographic representations. The network checks that the funds being spent match the transfer, the remaining balance and the required fee.

Bulletproofs range proofs let the network check that hidden values are within permitted bounds. Digital signatures confirm the authority to spend the corresponding funds.

The network also checks the state of the records being spent. After a confirmed spend, reuse of the same source records is rejected. Copying a PNG therefore creates no additional funds or right to repeat an already completed operation.

These checks work together: each verifies a particular condition of transfer validity.

Apply through Tagl ID: provide your first and last name and Gmail address, link to two social profiles, and briefly describe yourself and your experience. We review applications manually. If your application passes the initial review, we tell you which social profile to temporarily place a verification code on and ask you to verify your email address. Applying does not guarantee an invitation.

Applications are accepted only through Tagl ID. We do not offer tester places in unsolicited private messages or contact people first unless they have applied. Applying, verification and admission are free. Anyone offering another way to join or requesting payment for participation is not acting on behalf of TAGLS.

Your application remains in your TAGL. We can view the information you share until a decision is made. After acceptance or rejection, access to the application ends; only your Tagl ID and application status are retained to record the outcome.

More about verification and your information

Two profiles help us distinguish participants from large numbers of fabricated applications. Placing the code confirms that you control the profile we selected at the time of verification; it does not, by itself, verify your identity. Gmail provides an additional barrier against spam, and we verify that you can access the address you supplied.

Your name, introduction and profile links are used to review your application. You share them through Tagl ID for the verification period only; we do not keep a permanent copy of the application. This process does not require your email or social account passwords, login codes for those accounts, or your TAGL PIN.

A TAGL is a collectible digital object in the form of an image. Each instance has a name and a number within its edition. Once activated, the image also serves as a TAGLS wallet: it contains an identifier, encrypted keys and information needed to interact with the network. Its collectible value is displayed separately. Artists, performers, brands, game studios and other issuers can create their own editions.

A TAGL can be shared as an image. For a Ghost transfer, the sender creates a PNG with a specified amount of TAG or an LS Token and passes it to the recipient. The recipient opens the image in the wallet and confirms receipt; the decentralized network records the operation. Simply copying or changing the PNG does not, by itself, change the network balance.

More about transfers and protection

PIN1 is used to enter the wallet. A separate payment PIN2 is required to confirm a transfer, including Ghost, and pay for a network operation. Choose different, long and unpredictable values for the two PINs.

Ownership shares in a TAGL are tracked separately from the amount of TAG and LS Tokens it contains. A new TAGL, including one received in a drop, can have a single owner with a 100% share even when it has no liquidity. Adding liquidity does not, by itself, change the ownership share; transferring a share changes the percentages held by its owners.

The collectible value of the TAGL itself is displayed in its corresponding rarity token: rTAG or r(LS). The sender can choose to show their TAGL to the recipient, including the name, rarity and collectible value of the instance the funds came from.

Passwords are processed with Argon2id: checking each guessed value requires time and memory. The payment key is additionally protected by Split KDF. To unlock it, the wallet combines the result of processing PIN2 with a response from the Tagl ID server. The server holds its own secret for this response, but does not store your PIN2 or an unencrypted private payment key. A copy of the PNG alone therefore does not allow unlimited offline guessing of PIN2: requests to the server are rate limited. A short or predictable PIN remains unsafe; protect the original PNG, its backups and your recovery phrase.

An image can be associated with digital assets and services in TAGLS. The rights associated with a particular asset are defined by its issuance terms.

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.

More about key protection

Argon2id increases the cost of guessing a PIN. HKDF is used to derive separate keys for different functions. Split KDF additionally protects access to the payment key, as explained under “What is a TAGL?”.

TAG is the token of the TAGLS base network. TAGLS does not accept applications from exchanges to list it. TAGLS itself and market participants can sell TAG through Ghost: the sender passes the buyer a TAGL image with a specified amount of tokens, and the buyer opens it in the wallet and confirms receipt.

Declining listing applications does not prohibit resale of TAG, make its price stable or guarantee that its price will rise.

What about LS Tokens?

LS Tokens are created for specific useful functions of products on TAGLS. Their creators choose how to sell and distribute them, including directly, through the market or through exchanges.

Creators must follow the applicable requirements for their products and distribution methods.

Creators can issue digital objects and create applications, websites and programs packaged in a .tagl container. They choose how to distribute their products.

For example, in the Ticktagto concept, an artist issues tickets as TAGL images and offers them to their audience through Discord, Telegram, Instagram or TikTok.

.tagl is a universal format for digital products: applications, websites, books, music and other content. The creator packages the product and defines its access terms. When purchasing an application, the user receives a personalized .tagl file containing their instance of the product. Everything needed to try, pay for and use it can be brought together in one interface.

The product requests functions through a restricted bridge. The trusted Utility verifies the user's rights and permits only the allowed actions, without sharing the wallet's keys with the product.

More about access, payment and resale

The creator can offer demo access and different purchase options directly in the product interface: full access without a time limit, access to part of the product or a particular feature, or use for a defined number of days or hours. Selected capabilities within the application are paid for with the creator's LS Token. The network confirms the purchased rights, and the Utility unlocks the corresponding capabilities.

The product can be resold through a transaction on the network. The new owner receives their own instance; the previous owner loses network rights to further use, and the creator receives the commission specified in the terms, in their own token. Simply copying a purchased personalized file does not change its owner or give another user access to the application's protected functions. The network cannot delete content that has already been revealed.

A TAGL associated with a game, book, application or access rights to another product is protected from automatic spending by default. The wallet does not use its shares or liquidity as a source for ordinary payments, network fees or consolidation when creating a Ghost. This helps preserve the purchased product and its associated rights.

This protection also applies when a utility TAGL is the wallet's main TAGL. It does not prevent use of the product or an explicit transfer or sale of its rights under the issuance terms. Such an ownership change requires separate confirmation from the user.

Yes. The creator sells access to their product, receives revenue through their legal entity and pays the applicable taxes themselves. The customer receives an LS Token embedded in a TAGL. LS records the customer's share in the digital TAGL object; the rights associated with that share are defined by the issuance terms. The customer can hold, transfer or sell their share to other users on the P2P market.

More about purchasing and access

The creator defines the rights associated with a share in a digital TAGL: access to the whole application, individual features, a defined period of use, or other goods and services they provide. The buyer pays by card, bank transfer or cryptocurrency where permitted and receives a TAGL with the LS Token embedded in it. The LS received is accounted for through the shares owned by the buyer; associated rights are defined by the issuance terms.

For each LS Token, TAGLS Wallet shows the associated TAGLs, the user's share in each and the total balance. The balance is the sum of the share units owned by the user across those TAGLs.

The product terms explain whether holding a particular share is sufficient for access or whether LS must be used to pay for a selected capability. The Utility verifies the user's rights and unlocks the permitted capabilities. If the owner transfers or sells a share to another person, access follows the new ownership state and the product's rules.

The creator defines the sale and access terms, accepts payment and follows the applicable requirements for taxes, payments and buyers' rights. The product terms explain which capabilities the buyer receives and how they are accounted for through LS and TAGL.

Applicable rules must be checked in every country where the product is offered, including the EU, the US, Russia, South Korea and the UK.

The creator sells a product or access to it and provides the buyer with a TAGL containing the corresponding LS Tokens. The buyer pays by card, bank transfer or another permitted method.

Within a .tagl application, the user can pay for selected capabilities with the creator's LS Token. The product terms explain what access requires: ownership of a particular share or payment for a specific capability.

The TAGL accounts for the user's tokens and shares. The personalized .tagl file contains their instance of the product, while the Utility verifies their rights and unlocks the permitted capabilities.

LS (Layer Stega Token), also called a Stega Token, is a creator's token in TAGLS. It is used to account for shares in digital TAGLs. The creator specifies what a share provides, such as access to an application, its features or services.

How are shares and balances displayed?

For each LS Token, TAGLS Wallet shows the associated TAGLs, the user's share in each and the total balance. For example, you have 15 LS in TAGL #125 and 5 LS in TAGL #126: 20 LS in total. If the creator sells one LS for $1.50, the value of your shares at that price is $30. The rights associated with each TAGL are described in its issuance terms.

The collectible value of the TAGL itself is displayed separately in rTAG or r(LS).

Stega Token is TAGLS terminology for tokens used within its model of TAGL ownership and image-based interaction. TAG is the native token of the base network. Creators issue LS Tokens to account for shares in digital TAGLs; associated product rights follow their issuance terms.

The term describes the technical model. The legal treatment of a token, product or service depends on its characteristics, use and applicable law.

Yes. A wallet owner can provide an auditor with information to verify their operations. The auditor can run their own anchor and compare the supplied information with the network's records. Both transaction privacy and independent verification are therefore part of TAGLS's architecture.

What information is used for verification?

To verify a particular operation, the owner supplies information that allows its network record to be located and the disclosed data to be checked.

In the current implementation, the wallet can create a Payment Proof for a confirmed outgoing protected TAG transfer. The proof contains the operation identifier, network epoch number, payment amount and cryptographic data for checking its correspondence to the network record.

The verifier can confirm that the operation appears in network records and that the disclosed amount matches the cryptographic commitment. Records from the corresponding epoch are needed; the availability of historical records depends on the anchor used.

PIN1, PIN2 and private payment keys are not included in a Payment Proof. Sharing this proof does not, by itself, grant the right to spend funds.

The proof and its verification link contain the disclosed information. The owner chooses whom to provide them to.

The scope of verification depends on the materials supplied. Checking a set of operations, information about the parties and payment purposes may require additional records and documents.

Tagl ID is for signing in to websites and confirming information; TAGLS Wallet is for managing TAGLs, TAG and other assets. Both use a TAGL but serve different purposes. With Tagl ID, you sign in to services, confirm the information they need, store keys for third-party services and can use it for two-factor authentication. In the wallet, you view shares and transfer history, and receive and send tokens.

TAG is the native Stega Token of the TAGLS base network, used for purposes including network fees. TAG can be held in a TAGL and transferred between owners. Holding TAG does not give you a share in the organization operating the project; rights to a digital or physical object associated with a TAGL are defined by its issuance terms.

The base network fee is 0.001 TAG or 0.001 rTAG per transaction. For gas payments, 1 rTAG is counted as 1 TAG. Before confirmation, the wallet shows the fee, the payment token and the source of the deduction.

Spending rTAG reduces its remaining balance and the displayed collectible value of the TAGL. TAGLs protected from automatic spending are not used as a source for fees. If a product action requires several transactions, the total fee is the sum of their costs; the price of the product itself is accounted for separately. The amount in conventional money depends on the price of TAG. The gas calculation rule does not determine the market price of rTAG.

The presale uses a fixed TAG price; participation in the beta does not provide an individual discount. The price, how to obtain TAG and the other participation terms are published in the official presale terms.

No. Different projects can use the same ticker. The name TAG alone does not establish that a token belongs to the TAGLS network. This FAQ currently contains no purchase links.

TAG is the native token of the base network and is used, among other things, for network fees. An LS Token (Layer Stega Token) is issued by a product creator; its issuance terms can provide access to the product, individual features, services or other offerings from the creator. These tokens serve different purposes.

It is a TAGL associated with a particular digital or physical object. Its rules identify the issuer, describe the object and specify the rights provided by ownership of a share. The network helps verify the digital record and changes to it; the issuer defines rights to the object itself in the issuance terms.

An issuer is the creator of a TAGL edition who provides information about the object and defines the terms of its associated rights. This can be an artist, performer, brand, game studio or another creator.

For example, artist and architect Alex Petunin could issue a TAGL with terms for commercial use of the artwork: allowing the buyer to print one copy and display it in their own commercial premises. This is one possible scenario; the terms of different editions can vary.

Yes. An issuer can change the issuance terms. The process for making changes and whether they apply to previously acquired shares must be stated in terms available to the buyer before purchase.

Yes. The recipient receives a share of the TAGL used as the source of the transfer. For example, if you own 100% of a TAGL containing 100 TAG, sending 50 TAG gives the recipient 50% of that instance.

If you own 50% of a TAGL with your 50 TAG, sending 40 TAG leaves you with 10% of the instance and gives the recipient 40%. The transfer amounts in these examples exclude fees. The wallet shows changes to shares before confirmation. Rights associated with the received share are defined by the issuance terms.

Your main TAGL is the one you used to enter the wallet. You can protect its liquidity from being spent on transfers in the settings. For an ordinary wallet TAGL, this protection is off by default; a utility TAGL is protected by default, including when used as the main TAGL.

A protected TAGL can receive funds, but the wallet does not use it as a source of automatic spending. If there is not enough available unprotected liquidity, the wallet offers to change the amount or protection settings. An explicit transfer or sale of rights to a product requires separate confirmation under its issuance terms.

The wallet chooses a suitable unprotected TAGL with the required token and shows it before confirmation. If liquidity from several TAGLs must be combined for a Ghost transfer, the wallet first collects it in one suitable TAGL. If no other suitable instance is available, it uses the main TAGL with protection switched off. It then creates one Ghost for the specified amount.

Utility TAGLs are excluded from automatic selection by default. If no suitable unprotected source is available, the operation is not performed.

Yes, if the issuer has linked the specific item to its digital passport and provided a way to verify that link. The network can confirm the record and the issuer's authority. Checking the item itself remains part of the process the issuer is responsible for: a record of an authentic item does not make a counterfeit authentic.

rTAG (Rarity TAG Stega Token) is a rarity token associated with a TAGL's collectible value. It reflects the object's rarity and is one factor in assessing its collectible value. A TAGL associated with an LS edition uses the corresponding rarity token, r(LS).

rTAG can also pay network fees: for gas calculations, 1 rTAG is counted as 1 TAG. Spending rTAG reduces its remaining balance and the displayed collectible value of the TAGL.

When your share is fully spent, the remaining rTAG or r(LS) you own that is associated with that TAGL is automatically moved to your main TAGL.

Separate manual transfers of rarity tokens between TAGLs are not permitted. Automatic movement follows the network's rules. Ghost operations involving rarity assets are also supported.

The wallet displays the value of shares separately from a TAGL's collectible value. For example, 20 LS at the creator's price of $1.50 per unit gives a share value of $30 at that price. The collectible value of a TAGL is shown in its corresponding rarity token: rTAG or r(LS). The participants determine the price of a P2P transaction outside TAGLS.

Burning removes an instance from circulation when its liquidity has been moved to other TAGLs and no owners remain in the original instance.

Transferring the last share you own to another person removes the TAGL from your wallet. The instance continues to exist with the recipient. The sender's remaining rTAG or r(LS) moves to their main TAGL under the network's rules.

A saved image of a burned TAGL can remain with the user, but network rights to the burned instance end. A zero TAG or LS balance does not, by itself, mean burning: a TAGL without liquidity can still be 100% owned by its holder.

Inviting new participants through the referral program is unavailable during the private beta. It is planned to open when the first products become available that participants can share with people they invite.

Yes. Private beta participants can search the test pipeline and its results. It helps them see which scenarios have already been checked and propose new ones. A test result applies to the scenario tested, not to the entire protocol.

Yes. The private beta offers bonuses for discovered bugs. The program rules determine which findings are accepted and how rewards are issued. Participation in testing alone does not guarantee a payment.

Keep the original TAGL file and backup copies that you can open and verify. Send PNG files without compression or conversion: a service can change the embedded data even if the image looks unchanged. Supported wallets offer an optional encrypted backup through Tagl ID; opening a restored file still requires a PIN.

Preserve the original TAGL file and send it without compression or conversion. Image services can alter embedded data even when the picture looks unchanged.

TAGLS is developing deepX to improve resilience to image transformations. Supported formats, transformations and recovery limits will be documented for each released capability.

Yes. An independent audit is planned after the private beta; TAGLS will separately announce the audit and its results. The anchor's source code is open.

An anchor is a TAGLS network node with open source code that participates in verifying and storing network records. User transaction flows are not disclosed to everyone who examines an anchor. With a wallet owner's consent, an auditor can run their own anchor and compare information supplied by the owner with the network.

The image stores encrypted keys, an identifier and information needed by the wallet. The decentralized network confirms operations and the current distribution of shares. Simply copying or changing the PNG does not, by itself, change the network balance.

Copying the PNG creates another copy of the file. It does not create additional tokens or ownership rights. The wallet checks the network's current state when performing a network operation.

It is a transfer through a TAGL image: the recipient acquires the corresponding ownership share in a TAGL. The sender creates an image with a specified amount of TAG or LS and passes it to the recipient. The recipient opens the image in the wallet and confirms receipt; the decentralized network records the result.

An ownership share shows what percentage of a particular TAGL belongs to you. The amount of TAG or LS Tokens is accounted for separately: a TAGL can be 100% yours even with a zero balance. Adding funds does not, by itself, change the ownership percentage.

When funds are transferred from a TAGL, the corresponding part of your share passes to the recipient. The wallet shows the change in shares before you confirm the transfer.

The new owner receives their own instance of the product and access rights under its issuance terms; the previous owner loses network rights to further use. If the terms provide for a creator commission, it is credited automatically when the transaction is confirmed. The network cannot delete content the previous owner has already saved separately.

Losing a PNG, a PIN and a recovery phrase are different situations. A lost or damaged file can be replaced with a backup or restored from an enabled encrypted backup through Tagl ID. TAGLS does not store PIN1, PIN2 or your recovery phrase and cannot issue them again.

Tagl ID lets you store keys for third-party services and use them for two-factor authentication. These keys belong to the corresponding services and are not TAGLS payment keys.

A TAGL is a collectible object in the form of an image that also serves as a wallet once activated. A .tagl file is a container for a digital product: an application, book, music or other content with access terms defined by its creator. These formats serve different purposes.

The TAGL accounts for the user's tokens and shares. The personalized .tagl file contains their instance of the product, while the Utility verifies access rights associated with the TAGL.

The Utility is a trusted part of the system that verifies the user's rights and permits the application's allowed actions. The application accesses it through a restricted bridge, for example, to check access or request payment. The wallet's private keys are not shared with the application.