Conversation
Add the WARD Token MiCAR white paper as a new page under the $WARD section of the developer docs, drawn up in accordance with Regulation (EU) 2023/1114. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
📝 WalkthroughWalkthroughThis PR introduces a complete MiCAR white paper for the WARD token. The document details regulatory compliance, token characteristics, issuer information, offering mechanics, technical architecture, governance structure, underlying technology, and comprehensive risk disclosures across nine regulatory sections (Parts A–I). ChangesMiCAR White Paper Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/developer-docs/docs/ward/micar-whitepaper.md`:
- Line 470: The table row showing "Decimals: 6" in micar-whitepaper.md needs an
explicit cross-reference noting the discrepancy with other docs that show
"Decimals: 18"; update the "Decimals" table row (the table cell labeled
Decimals) to include a short inline note like "See note: decimals differ in
other docs (18) — tracking issue #<ID>" or a link to the tracking issue/PR so
readers aren't confused; ensure the note appears adjacent to the "Decimals"
value and use a consistent wording so automated docs checks can find it.
- Line 96: The document contains three conflicting dates for the same event
("June 1st, 2026", "February 3, 2026", "2026-01-06"); pick a single canonical
date model (e.g., Listing Date vs Publication Date vs Admission Date), decide
which exact date should apply to each label, and update every occurrence to that
canonical label and format (choose one format such as "YYYY-MM-DD" or "Month D,
YYYY") so all references match; ensure the phrases around the tokens (e.g.,
"Token Listing Date for EU", any timeline entries mentioning February 3 and
2026-01-06, and the whitepaper summary paragraph about admission/listing) are
relabeled explicitly (publication vs listing vs admission) and harmonized across
the document.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 53be5359-1b3a-42e9-9dc9-8cdece75c76b
📒 Files selected for processing (1)
docs/developer-docs/docs/ward/micar-whitepaper.md
|
|
||
| Admission to trading is sought to enable WARD to be admitted to trading on platforms for crypto-assets in the EU. | ||
|
|
||
| The initial total supply is 1,000,000,000 WARD. The circulating supply at listing will represent approximately 25.03% of the total supply (250,320,000 WARD), with a fully diluted valuation of approximately USD 2,270,000. Token Listing Date for EU: June 1st, 2026. Distribution will occur via direct listing on centralized and decentralized exchanges; no public sale, IDO or IEO has been conducted. An airdrop program is available through the Warden App for eligible users based on activity and social engagement, with vested allocations automatically staked and bonus incentives of up to 500% for users who lock rather than immediately withdraw. ProtoWardo Ltd expects the token to be admitted to trading on leading EU-based crypto-asset platforms that operate in full compliance with MiCAR. |
Contributor
There was a problem hiding this comment.
Resolve contradictory listing/admission dates before publishing.
The document currently states three different dates for the same event timeline (Line 96: June 1, 2026, Line 284: February 3, 2026, Line 491/495: 2026-01-06). This is a material correctness issue in a regulatory white paper and needs one canonical date model (e.g., publication vs listing vs admission), with labels made explicit.
Suggested edit pattern
- Token Listing Date for EU: June 1st, 2026.
+ Planned EU listing date: 2026-06-01.
- - **Q1 2026**: token listing event (February 3rd, 2026) on major CEXs and DEXs; ...
+ - **Q1 2026**: token listing preparations on major CEXs and DEXs; ...
- **9. Starting date of offer to the public or admission to trading**
- 2026-01-06.
+ **9. Starting date of admission to trading (planned)**
+ 2026-06-01.
- **10. Publication date**
- 2026-01-06.
+ **10. Publication date**
+ 2026-01-06.As per coding guidelines, "**/*.md: Assess the documentation for misspellings, grammatical errors, missing documentation and correctness".
Also applies to: 284-284, 491-495
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/developer-docs/docs/ward/micar-whitepaper.md` at line 96, The document
contains three conflicting dates for the same event ("June 1st, 2026", "February
3, 2026", "2026-01-06"); pick a single canonical date model (e.g., Listing Date
vs Publication Date vs Admission Date), decide which exact date should apply to
each label, and update every occurrence to that canonical label and format
(choose one format such as "YYYY-MM-DD" or "Month D, YYYY") so all references
match; ensure the phrases around the tokens (e.g., "Token Listing Date for EU",
any timeline entries mentioning February 3 and 2026-01-06, and the whitepaper
summary paragraph about admission/listing) are relabeled explicitly (publication
vs listing vs admission) and harmonized across the document.
| | Blockchain | Warden Chain (Cosmos SDK with EVM module) | | ||
| | Token Standard | Native chain token (not ERC-20) | | ||
| | Total Initial Supply | 1,000,000,000 WARD | | ||
| | Decimals | 6 | |
Contributor
There was a problem hiding this comment.
Add an explicit cross-reference note for the decimals discrepancy.
This page states Decimals: 6 (Line 470), but the PR context indicates another page still shows 18. Add an inline note or link to a tracking issue so readers don’t get conflicting token metadata.
As per coding guidelines, "**/*.md: Assess the documentation for misspellings, grammatical errors, missing documentation and correctness".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/developer-docs/docs/ward/micar-whitepaper.md` at line 470, The table row
showing "Decimals: 6" in micar-whitepaper.md needs an explicit cross-reference
noting the discrepancy with other docs that show "Decimals: 18"; update the
"Decimals" table row (the table cell labeled Decimals) to include a short inline
note like "See note: decimals differ in other docs (18) — tracking issue #<ID>"
or a link to the tracking issue/PR so readers aren't confused; ensure the note
appears adjacent to the "Decimals" value and use a consistent wording so
automated docs checks can find it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
$WARDsectiondocs/developer-docs/docs/ward/micar-whitepaper.md; appears in the autogeneratedwardsidebar at position 7 (after Supply):::warningadmonition; numbered MiCAR fields are preserved as bold labels and tables for readabilityNotes for reviewers
Decimals: 6for WARD; existingintroduction.mdlistsDecimals: 18. Preserved the source's value here verbatim — flagging the discrepancy for someone to reconcile in a follow-up if needed.