Issuer guide

Lydiaan Protocol turns a financial instrument — shares, a loan note, a preference share, units in a fund or a sports league — into a token investors can buy. You describe the instrument and back it with documents; Lydiaan reviews it; a token is recorded on a public blockchain; and everything that happens to it afterwards — an offering, a dividend, an interest payment, a buyback, a vote — is run on the platform and recorded against the same token.

You work in the issuer portal: instruments and their offerings, the token page investors see, your investors and orders, the corporate actions, your documents, announcements and reports, and your company page.

Nothing an issuer authors reaches investors without a second pair of eyes, and nobody approves their own work. That one rule shapes every workflow in the portal.

Five instrument types are configured with their own terms: equity (dividends, voting, bonus issues, buybacks), debt (a coupon schedule and repayment at maturity), preference (a coupon, redemption at par and optional conversion into equity), units (valued at NAV, redeemable at NAV, with a fee structure) and fixed deposit (a fixed rate for a locked term). Sports leagues, teams and matches are units instruments created through the sports module.

Settlement is in USDC or USDT — never bank money — and sports tokens settle in LYD, the platform's own token.

Issuers do not sign up. After an enquiry and Lydiaan's assessment, Lydiaan creates an account for the company's representative and shares the sign-in details with you. Sign in at the issuer sign-in page; until your company is approved, the portal opens on the onboarding wizard.

Onboarding is a five-step wizard that saves as you go, so it can be finished across several sittings. Until it is approved, the rest of the portal stays closed: only onboarding, settings and the Help Center are available.

After submission the onboarding page shows that your submission is awaiting review, which usually takes one to two business days. Your answers and documents are locked while they are reviewed. Each required document is checked before the company can be approved, and an approved company unlocks the whole portal. If changes are needed, the onboarding page reopens with the reviewer's comment so you can correct it and submit again.

Once the company is approved, the dashboard opens with counts that matter to an issuer: active instruments, instruments pending your review, tokens, votes, investors and NAV submissions pending. Each is a link to its page.

Quick actions sit beside them — Review Instruments, Create Instrument, Submit NAV Report, Create Voting Event, Post Announcement, View Investors, Manage Documents and Token Offering — followed by recent activity across the company, with a View All that opens the full Activity trail.

Create Instrument opens a short wizard: your company, the instrument's name and symbol, and its type. That creates a draft and lands you on its detail page, whose Configure button opens the editor. Sports tokens take the same path from the sports module, pre-filled with the league, team or match they belong to.

The editor is organised into sections, each a layer of the instrument's terms: general information, the economic terms (and, by type, the coupon and interest schedule, maturity and redemption, equity terms, units strategy and fee structure, fixed deposit terms, dividend and liquidation rules, conversion rules), governance, tokenomics — the raise plan the token is minted from — collateral, custody, investor rules (geographic rules and investor requirements), and documents.

Every section except custody must be individually approved before the instrument can be approved, so each is written to be reviewed on its own. The documents section shows a requirements checklist for the instrument type; the Documents chapter explains it.

Run Validation checks the instrument against the same rules the workflow applies at submit, approve and publish — required sections filled, required documents linked, terms consistent — so nothing is refused at submission that the editor did not warn about. Submit sends the instrument for review; a submission can be pulled back to draft until a reviewer has opened it.

An instrument moves through these states. Review starts automatically the first time an admin opens the submission. Request changes returns it to draft with a written reason and resets every section's approval; the content itself is kept, so you edit and resubmit rather than start over. Approval locks the terms; publication — a super admin's act — writes the token to the chain and opens it to investors.

A Token Offering is created against a published instrument. Five kinds exist, and they are the same five investors meet on the marketplace.

An offering is drafted by you, reviewed by the Lydiaan team, and runs once approved. Its states are the words its page shows.

An open offering appears as a marketplace card and on the token page's offerings tab, with one call to action that follows the window: Invest Now while open, the opening date before, Closed after, Not Eligible where your investor rules exclude someone, and Claim once an initial token offering is finalized. Investors take part from their own wallet — two signatures, approve then invest — and the contract enforces your minimum, per-investor cap and hard cap.

Token Offering decides what a round sells; the Token Page CMS decides how the token's page reads. It is a layout editor over a registry of sections — about, terms, capabilities, documents and the rest — with presets for each channel: the default marketplace layout, T20 for cricket, Liquidbrix for property. A token presented through more than one channel has one layout per channel.

The page displays the instrument's figures; it does not store them. A field that is not set in the instrument configuration shows as a blocker on the page, and is fixed in the instrument, not in the CMS.

A layout is edited as a draft and goes through the same review as everything else: submitted, approved by the Lydiaan team, then published. Publish eligibility is checked before the button works, and the blockers — a required section missing, a required field unset — are listed inline.

Tokens lists every token issued by your company with its symbol, name, total and available supply and current price, and links to the token's page and its instrument.

Investors lists every holder of your company's tokens: investor name, email, wallet address, the token and instrument they hold, that instrument's type and sector, and the quantity held with the amount invested. Totals for unique investors, tokens held and capital invested sit above the table.

You see holders of your own tokens only. The register is served by an issuer-scoped database function that narrows the request to tokens of companies linked to your account and records each access, so investor records are never read directly.

Search spans investor name, email, wallet address, token, instrument and instrument type at once. Filters narrow the register to one instrument type or one sector, and any column — investor, token, instrument, quantity or amount invested — can be sorted either way. Clear filters returns the full register.

A corporate action is something a company does to tokens it has already issued: paying out on them, issuing more, repaying them, changing what they are, buying them back, or putting a decision to the people who hold them.

Most of them run the same way — someone drafts it, the other side approves it, a Super Admin publishes it, and then the lifecycle runs. This tour is one stop on each of the ones you can reach from here.

A buyback is the company offering to buy its own tokens back from holders at a set price, up to a set limit.

The company fixes a price per token, a total token limit, and a deadline. Holders choose whether to sell into it; nobody is obliged to.

Capacity is first-come, first-served against the token limit. The remaining capacity is shown live on the campaign, and once it is gone the campaign is oversubscribed and stops accepting more.

Tokens bought back are retired, so the total supply falls and everyone who did not sell owns a slightly larger share of what is left.

A bonus issue gives existing holders extra tokens for free, in proportion to what they already hold. No money changes hands.

The issuer sets a ratio — for example one new token for every four held. On the record date the platform snapshots holdings and works out each holder's entitlement.

Unlike a dividend, a bonus is not a payout: it is new tokens minted to existing holders. Everyone's token count rises together, so nobody's share of the company changes.

Holders claim their entitlement during the claim window. Anything unclaimed when the window closes is handled at finalization.

A conversion turns a holder's debt into equity at a fixed ratio — they stop being a lender and become a shareholder.

The issuer sets a conversion ratio as a numerator over a denominator. Equity received = debt converted × numerator ÷ denominator.

The result always rounds down to a whole token. The remainder — the dust — cannot be converted, and the platform flags it before you commit.

Conversion is immediate and irreversible. The debt tokens are retired and the equity tokens are issued in the same step; there is no request queue and no pending state to wait through.

A dividend pays cash to everyone holding a token, in proportion to how much of it they hold.

The issuer sets aside a total pool and a payment date. On the record date the platform takes a snapshot of who holds the token and how much, and the pool is divided across those holdings.

The issuer then funds the pool in the payment token, and the platform distributes it. Holders do not have to do anything — the money arrives against the holding they already had.

A redemption is the end of a debt instrument's life: the issuer repays the principal and the tokens are retired.

At maturity, the issuer owes each holder the face value of what they hold. The redemption record is where that repayment is set up, funded and run.

The issuer funds the full repayment amount before anything opens. Once it is funded, holders redeem — they give up their tokens and receive the principal back.

This is a one-way door. Redeemed tokens are retired, not returned to circulation.

An interest schedule is the repeating coupon a debt instrument pays its holders — the rate, the dates, and every payment that follows from them.

The issuer sets a rate and a frequency — say 8% a year, paid quarterly — and the platform generates the full calendar of coupon dates from them.

On each coupon date, holders are snapshotted and each one's payment is worked out from the holding they had. The schedule keeps running until the last coupon is paid.

One schedule covers the whole life of the instrument. You do not create a record per payment; you create the schedule once and the payments follow.

Voting is how token holders decide company resolutions — one vote per token held at the snapshot.

A resolution is authored, approved, and then frozen against a holder snapshot. That snapshot fixes everyone's voting weight — trading after it does not change your vote.

Resolutions come in two kinds. A binary resolution is For or Against. An elective resolution offers between two and ten custom choices.

Ordinary resolutions pass on a simple majority of votes cast. Special resolutions must also clear a quorum and a higher threshold before they can pass.

After voting closes the result is finalized — a separate approval track from the authoring one, so a resolution can be approved but not yet finalized.

A units instrument is valued at its net asset value per unit, and that figure comes from you. The NAV page lists your published units instruments and your submission history; a new submission names the instrument, the NAV per unit, the total assets under management, the effective date and your notes on methodology and sources.

A submission moves from Draft to Submitted, and is then Approved or Rejected by the Lydiaan team. The latest approved NAV is what the token is valued and redeemed at.

Every action has its own page under Corporate Actions in the sidebar, listing its records with their current stage.

Open any of them and press the ⓘ beside the page title for that action's full guide — how it works, who approves what, the words it uses, and every stage it moves through.

An announcement is a proposal until it is published. Draft it, submit it, and it goes under review; an approved announcement is published — immediately or on a schedule — and later expires or is archived. A rejected one returns to draft with the reason. If a reviewer edits your proposal, it comes back to you for re-approval before it can go out. Publishing is never something you do yourself.

An announcement has a category (voting, dividend, bonus, meeting, token update, regulatory, general or custom), a severity, a body built from blocks — rich text, tables, images — and attachments from the document vault. Audience rules choose which holders receive it, and channel flags choose how: the register, notifications, email.

A published announcement appears in every eligible investor's Announcements register, on the token's page and on your company page's Announcements tab, and triggers the notifications the investor has opted into. Corrections, clarifications, updates and withdrawal notices are filed as follow-ups to the original so the record stays whole.

Every file your company uses on the platform lives in the vault: upload it once with a name, a type (financial, legal, corporate, compliance and so on), an optional period and description. A file is fingerprinted on upload, so the same bytes are never stored twice. Each document starts as a draft; once submitted it is verified or rejected by the Lydiaan team, and a rejection comes with the reason.

An instrument's Documents section lists what its type needs: hard requirements (a term sheet for debt and preference, corporate documents for equity), conditional ones switched on by other settings (a valuation for a secured instrument, a compliance certificate for certain jurisdictions, a collateral certificate for every collateral asset) and recommended placeholders a reviewer will look for. Each row shows how far the best matching link has got — Linked, Verified, On-chain — and the same rules block submission, approval and publication, so the checklist and the gate cannot disagree.

A document can only be linked to an instrument, a company-page section or a vote once its version has been deployed. Deployment is done by the Lydiaan team and signed from their wallet: the file is pinned to IPFS — publicly and permanently — and its hash is registered on the public document registry. Pickers show undeployed documents greyed out with the stage they are waiting on.

A deployed version is immutable. To change a document, upload a new version; it starts as a draft and goes through verification and deployment again with its own hash and transaction. Existing links stay pinned to the version they were made with, and the editor offers to update a link when a newer version is deployed; the older version is then revoked on the registry so it no longer verifies as current.

Investors see every document with its version, its hash, a link to the anchored copy and a live on-chain check, and can verify any file they were given on the public verifier without an account.

Reports generates a table on demand and lets you download it. Three reports exist today.

Activity is your portal's audit trail. It gathers what the platform already records against your company and puts it on one timeline, newest first: instrument lifecycle transitions with the reason given, voting events as they are created, approved, published or cancelled, announcements as they are drafted and reviewed, NAV submissions as they are submitted and reviewed, and documents as they are uploaded and verified.

Only your own company's history appears. The dashboard's Recent Activity panel shows the newest few; View All opens the full trail.

Search matches the event, the instrument and the description. The type filter narrows the trail to instruments, voting, announcements, NAV or documents, and a date range bounds it to a period. Each entry carries both how long ago it happened and the exact timestamp, and opens the surface that owns the record.

Every issuer has a public company page: profile, published disclosures, filings, version history, announcements, votes, events and the list of its tokens. Investors reach it from any of your token pages.

The content is authored by the Lydiaan team — managers assigned to your company — from the information and documents you provide, and every section is reviewed before it is published. Your Company Page in the portal is a read-only overview of that content: section by section, with each subsection's state (Not Started, Draft, In Review, Approved, Completed, Rejected), a preview that renders the page as investors see it, a View Public Page action once the company has a public address, and the document vault panel for supplying what the content needs.

Publishing is a single act over every approved subsection and produces a numbered version of the page. Editing a published subsection creates a draft overlay while the published content stays live, and the change goes through the full review again before it replaces what investors see. Earlier versions are kept and can be compared.

Settings shows your account and company information — registration number, country of incorporation, KYB status — and lets you set your avatar and the company logo that appears on your pages.

Connect Wallet sits at the top of the sidebar. An issuer needs a wallet as much as an investor does: funding a dividend pool and closing it out are signed from your own wallet, and the address that signs is the one any remainder comes back to. Linking it binds it to your profile, which is how the platform knows which wallet your company acts from rather than trusting whatever happens to be connected.

The wallet is yours; Lydiaan never holds its key. Nobody from Lydiaan will ask for a recovery phrase or a private key.

As a league operator you create a league — its seasons, teams and matches — and submit it for approval; the Lydiaan team reviews it and a super admin publishes it. League and team tokens are created through the instrument wizard with the sports link pre-filled; creating a match automatically generates a pair of draft match tokens, one per side, whose sale window is anchored to the fixture and closes at least an hour before the toss. There are no betting mechanics: a match token is an ordinary units subscription.

The sports overview shows your leagues with their token counts, the approval queue in both directions, upcoming matches with how full each side is, and live buybacks on your sports tokens. Proceeds settle in LYD to your company treasury; the exit for holders is secondary trading or a buyback you run, after which a fully bought-back match token can be burned as a retired edition.

What is being issued, sold and held.

Identity, custody and the on-chain side of the platform.

What can happen to a token after it is issued.

The contact page reaches the Lydiaan team. For a stuck submission, name the instrument or record and the state it shows; for a listing enquiry, use the issuer form. Nobody from Lydiaan will ask for your password, a recovery phrase or a private key.