# VERY Whitepaper
2026.10 · English edition · First published 2026-10-01
# 1. Beyond technology, into everyday life.
A world where everyone can connect, send and pay in familiar ways.
Updated: 2026-10-07
## Blockchain’s value begins with use
VERY brings blockchain into more people’s daily lives. Talk in a familiar messenger, select a friend’s profile to send assets, and pay by phone at a nearby store. We build experiences that let people do what they need before they have to study the technology.
We focus on people with easier access to a smartphone than a bank, people sending money to family abroad, and small-store operators who cannot readily adopt complex, expensive payment terminals. Blockchain can give them a more accessible foundation for finance and business.
## One network, connected daily life
**VeryChat** is where people meet. Conversations, channels and real-time translation build relationships, while the in-app **VeryWallet** connects free profile USDT transfers with asset management. Conversations continue across mobile, Mac and Windows. **VeryPOS** brings stablecoin payments such as USDT, plus order, product and sales management, to a store’s phone. **VeryAds** is the advertising platform where businesses reach these users.
**VeryNetwork** is the ecosystem connecting these services, and **VeryChain** is VERY’s network foundation. Service roles and the coin’s role remain distinct, while the user experience is designed to flow naturally between them.
## Participation leads to use, and use returns to the ecosystem
VERY is distributed under defined rules to people who participate in and contribute to the ecosystem. Fruit harvesting and invitation rewards, with different halving criteria, bring users back to the app and connect new people. Channel participation and content viewing add further activity, leading to ongoing visits and app traffic.
Places where people gather and actively consume content give advertisers a chance to meet customers. VeryChat traffic forms the basis of that advertising demand. **VeryChat app advertising through VeryAds can be purchased only with VERY, so advertising demand translates into demand for actual VERY use.**
Of the VERY spent on ads, **50% is distributed as user rewards, 20% goes to node proof participants, and the remaining 30% is burned.** App advertising demand thus rewards users and network participants while burning some VERY. This connects participation and rewards, app traffic, ad demand, VERY use, redistribution and burning in an ecosystem cycle.
We aim for **a network where more people participate and VERY ownership is spread across more individuals**. As participation grows, we want VERY to be distributed more widely and used by its individual holders. Distribution, use, redistribution and burning support that circulation.
## The problem and our vision
### What problem are we solving?
Even when people can talk by smartphone, sending and receiving money may still be difficult or expensive. Cross-border transfers, inaccessible financial institutions and costly store systems limit everyday and economic opportunities.
Blockchain can underpin cross-border asset movement. But long addresses, network selection and preparing gas tokens become new barriers when exposed directly to users. VERY starts with product experiences that lower these barriers.
Connecting familiar actions to real blockchain use.
### Familiar actions become the entry point
A messenger makes it easy to understand whom you are sending to. Profile transfers in VeryChat reduce entry of hard-to-read addresses. Free USDT transfers reduce the need to first obtain a separate asset to pay gas.
Even when the app handles technical steps, confirming the recipient and amount must remain clear. Our product principle is to combine convenience with user control.
### Connecting to stores where assets can be used
The experience continues when transferred assets can buy goods and services. VeryPOS lets even small stores manage orders, products and sales and accept USDT on a phone. Customers choose items and quantities through the store QR; merchants check acceptance, payment and handover status.
Over time, we aim to bring blockchain payments, cash and existing local payment methods into one store workflow. [VeryPOS](/whitepaper/en/verypos/) distinguishes current availability from future integrations.
### Direction shared at GWDC 2026
The September 30, 2026 GWDC presentation described a strategy using a messenger as the entry point to connect wallets and store infrastructure. The aim is to let users make the transfers and payments they need without having to think about blockchain’s technical details.
Coverage of the presentation introduced profile transfers and support for sending BNB Smart Chain USDT without users first obtaining BNB. This describes **a product experience that reduces users’ cost and operational burden**; it does not mean the network’s processing costs disappear.
[Read the article about the GWDC presentation](https://www.tokenpost.kr/news/insights/416214)
### The adoption we aim for
Adoption should be assessed through repeated real use as well as registrations. What matters is whether conversations continue, transfers become easier, and stores can accept payments and manage their books.
VERY connects a global community, familiar UX, contribution-based distribution and real-world uses. Our vision is to turn technical capability into practical value in people’s lives.
## How to read this whitepaper
- New readers can start with [the problem and vision](/whitepaper/en/#vision).
- For the services, read the [ecosystem overview](/whitepaper/en/ecosystem/) and each product chapter.
- See [VeryAds](/whitepaper/en/veryads/) for advertising operations and campaign examples.
- For amounts and rules, see [tokenomics](/whitepaper/en/tokenomics/), [halving](/whitepaper/en/mining/) and [channel algorithms](/whitepaper/en/channels/#content-recommendations).
- Begin with [VeryChain](/whitepaper/en/verychain/) for node participation and technical information.
This edition translates the **Korean review text reflecting the website’s product and reward descriptions as of October 7, 2026**. It distinguishes service workflows, allocations by purpose, participation rewards and actual payment reports. [Policy consistency records](/whitepaper/en/references/#policy-record) separate confirmed policies from details requiring further verification.
Sources for this chapter:
- https://www.tokenpost.kr/news/insights/416214
---
# 2. One ecosystem, connected roles.
People, stores, advertisers and network participants meet through their individual needs.
Updated: 2026-10-07
An ecosystem viewed through what each participant does, rather than service names.
## The roles of four services
| Service | Who it serves | Core role |
| --- | --- | --- |
| VeryNetwork | Users, developers and node participants | Ecosystem direction, VERY policies, and connections between the network and contributions |
| VeryChat | People talking and connecting | Chat, channels, translation, wallet, transfers and rewards |
| VeryPOS | Store operators and paying customers | Stablecoin payments and order, product and sales management |
| VeryAds | Advertisers and the content ecosystem | VERY-based advertising and circulation of ad spend through the ecosystem |
VeryWallet names the wallet experience inside VeryChat. VeryChain is the mainnet’s name. The VeryPay merchant map helps people discover real places to use assets; it does not mean every registered store accepts every payment method supported by VeryPOS.
## The user journey
Someone may start using VeryChat to talk with friends. They can communicate across languages in channels, send USDT through profiles and find places to use it on the merchant map. VERY rewards for activity and invitations encourage contributions to the ecosystem and return visits.
## The store and advertiser journey
Stores manage payment and sales information with VeryPOS. They can run campaigns on VeryAds to meet new customers. Ad spend is paid in VERY; part is distributed to users, channels and node participants, and part is burned.
Stores using VeryPOS are not required to buy advertising. Advertising and payments are **separate uses** that can connect with one another.
## Distinguishing assets and rewards
- **Stablecoins such as USDT:** assets used for transfers and store payments.
- **VERY:** the ecosystem coin used for contribution rewards, advertising and payments at supporting stores.
- **Credits:** separate rewards used for app benefits, missions and the credit market.
Each asset type has its own usage conditions. VERY halvings do not reduce USDT balances or adjust credits by the same ratio.
## From participation to use
Fruit harvesting, invitation rewards, channel participation and content viewing give people reasons to visit the app. The resulting traffic creates opportunities for advertisers to reach customers, and advertising paid exclusively in VERY creates demand to use VERY.
Of the VERY spent on advertising, **50%** goes to users and channels, 20% to node proof participants, and 30% is burned. Stores may also accept VERY if the merchant chooses. [Advertising distribution and burning](/whitepaper/en/economy/#advertising-allocation) explains each use and its reporting basis.
## VERY withdrawn on-chain
The **operations team’s report dated 2026-10-05**, published on the website, combines VeryChat’s first and second KYC withdrawals with node withdrawals.
| Category | VERY withdrawn |
| --- | ---: |
| First KYC · 17,592 people | 195,756,065.6 |
| Second KYC · 98,839 people | 580,942,681.6 |
| **VeryChat KYC subtotal** | **776,698,747.2** |
| Node withdrawals | 1,197,084,303 |
| **Total** | **1,973,783,050.2** |
Node withdrawals were calculated as `2,000,000,000 − 802,915,697 = 1,197,084,303 VERY` on the same reference date. **Marketing amounts are excluded.** This report covers withdrawals within that scope; it is not a measure of total circulating supply.
Live node status and advertising distribution carry their own update times. We do not change this fixed report’s total by replacing just one component with a live remaining balance from a different date.
---
# 3. Everyday connections start with VeryChat.
Chat, channels, on-device translation, free profile USDT transfers, desktop access and everyday rewards.
Updated: 2026-10-08
## Why chat is at the center
VeryChat is a messenger that starts with friends’ conversations and leads to channels, translation, wallets and transfers. A person’s profile is the shared point of contact for talking and sending, reducing the need to type long addresses or open another app each time you change tasks.
One-to-one and group conversations maintain relationships; channels introduce people with shared interests. Transfer notifications and transaction history are also available in the familiar app.
## Five experiences
| Area | What you can do | Connected features |
| --- | --- | --- |
| Chat | One-to-one and group chats, transfer notifications | Profiles and wallet |
| Channels | Share posts, subscribe, comment and react | On-device translation and recommendations |
| Mining | Plant seeds and harvest fruit to earn VERY | Levels, friend boost and invitations |
| Benefits | Daily missions and walking | Credits and credit market |
| Wallet | View VERY and USDT, send through profiles and pay | VeryWallet and VeryPOS |
## Group conversations and community
Group chats support up to 10,000 participants. Creators can appoint co-administrators and manage the community with member ranks, pinned announcements, mentions, password entry and do-not-disturb hours. Token or NFT holding requirements and links between channels and group chats are also supported.
Channels share news through posts and comments. Discover new channels and popular content, then keep up with subscribed channels. Operations, recommendations and channel rewards that have not yet launched are described in [channels and community rewards](/whitepaper/en/channels/).
## On-device AI translation
### Real-time translation on your device
Understand messages in other languages without repeatedly leaving the conversation. Enable translation in a channel and on-device AI processes it locally. People around the world can speak their own languages while understanding one another.
Translation runs on the device; sending and receiving messages requires a network connection. Check the app for supported languages, model downloads and device-specific requirements.
### Future conversation summaries
On-device AI conversation summaries and saving to “Chat with myself” are future directions, distinct from the real-time translation currently available.
## Wallet and USDT transfers
### A wallet inside the app
VeryWallet is the wallet inside VeryChat for viewing VERY and USDT, sending and paying. **Users hold the private keys; the company does not store them.** Unlock it with a PIN, and manage your own device-change and recovery information.
The in-app wallet for checking assets and sending through profiles. Balances shown are demo data.
### Sending USDT through a profile
1. Select the receiving friend’s profile.
2. Select USDT and enter the amount.
3. Confirm the recipient and amount, then send.
4. Check the result in chat transfer notifications and wallet history.
Profile transfers reduce typing long wallet addresses. You still need to confirm the recipient to avoid sending to another account with a similar name or photo.
### Free transfers and network costs
**Supported profile USDT transfers in VeryChat have no transfer fee.** This reduces the burden of first obtaining a separate gas asset. External-wallet withdrawals, exchanges and other-network transactions follow their respective feature guidance.
### The roles of VERY and USDT
VERY is used for participation rewards, advertising and payments at supporting stores. USDT is a primary asset for profile transfers and store payments. Credits earned in Benefits are separate from both and used in the credit market.
### A wallet that connects to payments
Find places on the merchant map, order via store QR and pay with VeryWallet. Check order-screen conditions because supported assets and VERY limits vary by store. [VeryPOS](/whitepaper/en/verypos/) explains the full customer and merchant flows.
## VeryChat continues on desktop
VeryChat is available on iPhone and Android, as well as **Mac (Apple Silicon) and Windows**. On a larger screen, view your chat list and conversation together and move between channels, mining, benefits and wallet.
Conversations and wallet on one desktop screen. A demo account in the actual product.
| Screen | Desktop use |
| --- | --- |
| Chat | Chat list beside the selected conversation |
| Channels | Browse posts and channel conversations on a large screen |
| Mining | Check fruit harvest and friend boost |
| Benefits | Explore missions and the credit market |
| Wallet | Check assets and transfer notifications |
## Rewards connect participation
Fruit harvesting and invitations lead to VERY rewards, while daily missions and walking lead to credits. They give people reasons to return, meet friends and engage with content; that activity creates opportunities for advertisers to reach customers.
[Fruit rewards and halving](/whitepaper/en/mining/) and [invitation rewards and friend boost](/whitepaper/en/invitations/) explain VERY calculations. See [VeryChat downloads](https://verychat.io/en/download/) for installation and supported platforms.
Sources for this chapter:
- https://www.tokenpost.kr/news/insights/416214
---
# 4. USDT payments and sales management, all on one phone.
A blockchain payment and store-management platform that small stores can start using easily.
Updated: 2026-10-07
## Payments continue when stores can use them
VeryPOS is a **free store-management platform used on a phone without a separate POS terminal**. Centered on USDT stablecoin payments, it brings product registration, order intake, counter sales and sales history together.
Customers open a menu through the store QR, place an order and pay on their own phone. The aim is to give even small stores both a customer ordering interface and an operator interface.
## The basic payment flow
| Step | Customer action | Store checks |
| --- | --- | --- |
| Choose items | Open the store QR and view products and prices by category | Registered products and prices |
| Confirm order | Check quantities and total, add requests if needed | Received orders and requests |
| Choose payment method | Select USDT wallet payment or a method offered by the store | Awaiting-payment status |
| Pay | Include VERY if the store allows it | Status for each payment method |
| Complete | Check order number, items and payment result | Confirm payment, then hand over goods |
Choose items
Choose payment method
Payment complete
Product screens featured on the homepage. Stores and amounts are illustrative examples.
## Why stablecoins are central
Stores need a consistent basis for prices and sales records. VeryPOS uses USDT as a primary payment method, while merchants choose how to accept VERY.
| Payment method | Merchant choice |
| --- | --- |
| USDT | Receive payments from VeryWallet’s USDT. |
| USDT + VERY | Accept VERY up to the allowed proportion and the remainder in USDT. |
| VERY | Choose full payment, partial payment or no VERY. |
**The merchant sets the maximum VERY share and conversion basis.** “VERY 20% + USDT 80%” on screen is an example setting, not a fixed ratio for all stores. Cash, card and other counter-payment availability also follows store settings.
## Store operations for merchants
Add products and manage categories and prices. Separate incoming orders into awaiting-payment and paid states, then mark handover complete once goods are delivered. Counter orders can be added directly by searching products on the sales screen.
Sales history shows amounts and payment methods, with transactions grouped by statuses such as checking, completed and failed. Process orders by distinguishing a created payment request from a completed payment.
Order management
Product management
Sales history
## Registering and starting a store
1. Enter the store name customers will see.
2. Choose the currency for displayed prices. **Check carefully: it cannot be changed after creating the store.**
3. Choose an ordering flow suited to a retailer, restaurant, café or other business type.
4. Decide whether to accept VERY alongside USDT, and set the allowed share and conversion basis.
5. Register products and display the store QR to receive orders.
Merchant applications currently run on the separate VeryPay service. Apply as a merchant ↗
## A map of stores around the world
Find publicly registered stores on the [VeryPay map](https://pay.verychat.io/) and VeryPOS homepage. Search by store name or address, or select a small VERY marker to see its location and details. Zoom in and out to explore nearby stores.
The map is based on the **VERY-accepting merchant list**. Confirm each store’s support for USDT and other payment methods and its actual terms individually.
## Future expansion
The direction is to connect cash, familiar local payment methods and blockchain payments in one store workflow. Regional payment integrations will expand on today’s order, product and sales management experience.
Stores can also share news with customers through VeryAds. The 50/20/30 advertising distribution and store payments follow separate policies. See [VERY circulation and advertising distribution](/whitepaper/en/economy/) for the distinction.
Sources for this chapter:
- https://www.tokenpost.kr/news/insights/416214
- https://pay.verychat.io/
---
# 5. Connect business to people’s everyday lives.
Six ad placements, creative, budget and report management, POREMI campaign results, and plans for AI-assisted advertising.
Updated: 2026-10-07
## A VERY-only advertising platform
VeryAds helps businesses and services reach VeryChat users. Advertisers directly manage creatives, campaigns, budgets, schedules and performance reports. **Advertising runs exclusively on VERY.** Buying VERY and topping up the ad balance directly in the advertiser interface is planned.
Users encounter brands in chat, channel and reward screens. Advertisers choose placements that suit their message and run campaigns within a budget.
## Six ad placements
| Placement | Location and format |
| --- | --- |
| Rewards banner | Horizontal banner below rewards and above today’s benefits |
| Chat-list banner | Horizontal banner below the chat heading and above conversations |
| Channel ad | Image, text and action button within channel conversations |
| Icon banner | Small icon to the left of the mining-screen tree |
| Modal banner | Image panel and action button at the bottom of the mining screen |
| Splash | Ad at the top of the launch screen, with VeryChat branding below |
01 · Rewards bannerBelow rewards, above today’s benefits02 · Chat-list bannerBetween the chat heading and conversations03 · Channel adImages and content within channel conversations04 · Icon bannerLeft of the tree on the mining screen05 · Modal bannerImage panel at the bottom of mining06 · SplashAdvertising on the app’s opening screen
These are the same placement examples as the homepage. Creative and figures illustrate where ads appear and use demo data. Select a screen to enlarge it.
Creative specifications vary by placement. See examples at [VeryAds ad placements](https://veryads.io/en/formats/).
## Campaign workflow
1. Set campaign information and placement.
2. Enter the image, title, copy and destination URL, then check the phone preview.
3. Set total and daily VERY budgets and desired start and end dates.
4. Review, request approval, then check review status and delivery schedule.
**A budget is a spending cap, not an immediate charge.** Review approval and the start of delivery are separate steps. Check actual delivery and billing terms in the advertising platform.
Register images and copy and preview the selected placement. Campaign information is demo data.
## Measuring results in reports
Compare VERY spent, impressions, clicks and CTR by period and campaign. Review trends and export reports to plan the next campaign. CTR is calculated as `clicks ÷ impressions × 100`.
An actual product report screen with illustrative figures, separate from the POREMI campaign results below.
## POREMI — a real campaign
From **September 1–15, 2026, targeting international users outside South Korea**, ads ran on two placements: the mining-entry modal and the home-screen banner.
| Metric | Campaign result |
| --- | ---: |
| Signups tracked through the dedicated link | 26,768 |
| Impressions | 16,439,755 |
| Clicks | 435,111 |
| Overall CTR | 2.65% |
| Click-based spend | 870,222 VERY |
| Cost per signup | Approximately KRW 163 at the conversion rate then |
Campaign spend was calculated as `435,111 clicks × 2 VERY`. The 1,000,000 VERY budget differs from actual spend; the conversion basis at the time was `1 VERY ≈ 5 KRW`. This click price and exchange rate apply to this example.
Of all 26,768 signups, 20,600 (77%) watched at least one POREMI ad and 3,755 (14%) invited at least one friend. More than approximately 6,000 additional invitations is an **estimate** from the supplied invitation statistics, shown separately from dedicated-link signups.
Impressions and clicks come from VeryAds; signups and subsequent activity come from POREMI. See daily signups and placement results in the [website’s campaign data](https://veryads.io/en/#results).
## How is ad spend used?
Of advertising VERY, **50% goes to users and channels, 20% to node proof participants, and 30% is burned**. Ad demand creates real VERY use, which feeds participation rewards and supply management.
The website separately reports cumulative usage, community distribution, node distribution, burns and the buyback fund. The buyback fund is in USDT; other advertising usage and distribution figures are in VERY. Details are in [advertising distribution and burning](/whitepaper/en/economy/#advertising-allocation).
## AI advertising and MCP — planned
### VeryAds MCP — planned
We are preparing an experience that connects AI tools such as GPT and Gemini with VeryAds: describe a product and message, then move through banner generation, copywriting, budget and schedule setup, to campaign registration.
VeryAds MCP is planned. AI-prepared content still goes through advertiser review and ad approval.
For example: “Create a banner for our store’s new menu and register a campaign with a total budget of 5,000 VERY.” This is not presented as currently released automated delivery. Connection methods and permission scope will be explained at availability.
## Channels and external media
The six placements described here are inside VeryChat. Channel content and community activity underpin advertising; expansion to external media is a future direction. Check currently available inventory and conditions in the [advertiser platform](https://admin.veryads.io/auth/signin).
---
# 6. How is VERY allocated?
Community and marketing receive 56% of 10 billion VERY. Current allocation and the previous allocation record.
Updated: 2026-10-07
## Total supply and allocation
VERY’s total supply is **10,000,000,000 VERY (10 billion)**. **56%, or 5.6 billion VERY, is allocated to community and marketing.** The allocation below was **changed on October 7, 2026** and shows amounts by purpose, not current circulating supply or amounts already paid.
Changed 2026-10-07. Total supply remains 10 billion VERY and allocations total 100%.
| Category | Share | Allocated VERY | Purpose |
| --- | ---: | ---: | --- |
| Community and marketing | 56% | 5,600,000,000 | VeryChat rewards, marketing and node-validator rewards |
| Team and advisors | 19% | 1,900,000,000 | Development, operations, hiring and advisory |
| Treasury and grants | 5% | 500,000,000 | Service operations and ecosystem support |
| Investors (KOL round) | 10% | 1,000,000,000 | Investment for project growth |
| Liquidity provision (LP) | 10% | 1,000,000,000 | Liquidity for trading |
| **Total** | **100%** | **10,000,000,000** | |
## Inside the 5.6 billion community and marketing pool
This pool contains **3.4 billion VERY for VeryChat rewards, 200 million for marketing, and 2 billion for node-validator rewards**. “Share of allocation” below uses 5.6 billion as its denominator, distinct from the share of total supply.
Shares within the pool are rounded to one decimal place.
| Category | Allocated VERY | Share of 5.6B pool | Share of total supply |
| --- | ---: | ---: | ---: |
| VeryChat rewards | 3,400,000,000 | 60.7% | 34% |
| Marketing | 200,000,000 | 3.6% | 2% |
| Node-validator rewards | 2,000,000,000 | 35.7% | 20% |
| **Total** | **5,600,000,000** | **100%** | **56%** |
VeryChat rewards combine fruit, invitation, channel and other app-participation rewards. [Fruit halving](/whitepaper/en/mining/) covers seven stages through 2.2 billion cumulative VERY; [invitation rewards](/whitepaper/en/invitations/) use signup-based rates. These thresholds are not extra issuance. Fruit, invitation, channel and staking rewards have no separate fixed total allocations; each follows its own payment policy. Channel rewards have not launched.
## Distribution follows contribution
Contribution is not just one activity. Early-user invitations, ongoing participation, content and channel operation, and node proof contribute differently. App rewards are managed within the unified VeryChat pool, using calculation rules suited to each purpose.
Halving gives greater recognition to contributions while the platform is small, then slows new distribution as participation broadens. It is designed to share a defined supply among more people and manage distribution pressure.
## Allocation, unlock and circulation differ
Not all allocations immediately circulate on the market. Distinguish contractual unlocks, participation payouts, ecosystem holdings and actual trading or use. Whether LP allocations count as circulating also depends on actual holdings, transfers and reporting rules.
See [vesting](/whitepaper/en/vesting/) for unlocks and [fruit](/whitepaper/en/mining/), [invitation](/whitepaper/en/invitations/) and [node](/whitepaper/en/verychain/#node-rewards) policies for rewards. This allocation table alone cannot determine current circulating supply.
## Reading actual payout reports
Allocation is a budget, vesting establishes entitlement, and actual payout is delivery to recipients. Investment commitments and investor payouts are separate, as are team vesting and completed team payments. Unreported items are not displayed as zero.
The reference date and scope of published KYC and node withdrawals are in [ecosystem withdrawals](/whitepaper/en/ecosystem/#온체인으로-출금된-very).
## Use and redistribution
VeryAds uses VERY for ad spend. Redistribution to users, channels and nodes, plus burning, operates separately from initial supply allocation. Do not add the two sets of percentages or apply the advertising burn rate to total supply.
## Allocation change record
**2026-10-07** — Community and marketing increased from 5.1 to 5.6 billion VERY; treasury and grants decreased from 1 billion to 500 million. The former 2.9 billion total for invitations, fruit, channel subscriptions and staking was unified as VeryChat rewards and increased to 3.4 billion. Marketing 200 million, nodes 2 billion, team/advisors 1.9 billion, investors 1 billion, LP 1 billion, and total supply remain unchanged.
View previous allocation · before 2026-10-07
This preserves the previous allocation. The tables above define the current allocation.
Total supply is **10,000,000,000 VERY (10 billion)**, with **51% allocated to community** under the previous policy. These are purpose allocations, not circulating or already-paid amounts.
Previous top-level allocations total 100%.
| Category | Share | Allocation | Purpose |
| --- | ---: | ---: | --- |
| Community | 51% | 5,100,000,000 | App participation, node rewards and marketing |
| Treasury and ecosystem | 10% | 1,000,000,000 | Service operations and ecosystem support |
| Investors | 10% | 1,000,000,000 | Investment for project growth |
| Liquidity provision | 10% | 1,000,000,000 | Trading liquidity |
| Team and advisors | 19% | 1,900,000,000 | Development, operations, hiring and advisory |
| **Total** | **100%** | **10,000,000,000** | |
---
# 7. Actual payouts and vesting principles
Actual payouts and withdrawals by category, vesting, and payment after unlock.
Updated: 2026-10-08
## Schedule reference points
Allocated VERY follows distribution rules for each recipient category. Team vesting is measured from the **employment start date**, and post-listing lockup from the **listing date**. Future investor and KOL distributions follow the listing-related terms in their contracts. We do not calculate new calendar dates or completed amounts without verifying actual start dates, listing dates, individual agreements and execution records.
Amounts subject to lockup are **paid according to the recipient’s schedule only after the lockup has ended**. Actual payouts therefore mean amounts delivered to recipients after unlock. An unlocked amount that is still awaiting its payment date is classified as unpaid.
## Distinguishing amounts and stages
| Stage | Meaning | Payment status |
| --- | --- | --- |
| Allocation / investment commitment | Amount set for an individual or by contract | Different from amounts already paid |
| Vesting | Entitlement earned by meeting conditions such as service duration | Lockup and payment schedule still apply |
| Unlock | The restriction period has ended | Unpaid if the payment date is still pending |
| Actual payout | Delivery to the recipient has been completed | Counted as paid |
Investment-committed VERY and actually paid VERY are tracked separately, as are team-vested VERY and actual team payouts. This whitepaper does not estimate payout results that have not been supplied.
## Investors and KOLs
As of October 2026
VERY has built its services and grown without external investment to date. The investor and KOL allocation is reserved for future fundraising and partnerships; the KOL round has not yet taken place.
Lockup and vesting for future investment will be set by individual agreement. The KOL round allocation is **200 million VERY**, or 20% of the investor allocation. When the round takes place, the following distribution schedule is planned for participants who complete the specified ambassador activities.
| Planned KOL distribution | Share of that round’s allocation |
| --- | ---: |
| Before listing | 40% |
| 6 months after listing | 30% |
| 1 year after listing | 30% |
The KOL amount is included in the total 1 billion VERY investor allocation. It is not an additional issuance.
## Team vesting
VERY allocated to the team vests over 48 months (4 years) from the employment start date. 25% vests at the end of the first 12-month cliff, and the remaining **75% vests evenly each month over the following 36 months**. If a team member leaves before completing 12 months of employment, the vested amount is 0%.
A **12-month lockup after listing** applies. Actual payment of vested amounts is **made in installments on the defined schedule after unlock**. Separate recovery and payment terms apply when a team member leaves.
Advisor allocations follow individual agreements within the team and advisor pool.
## Treasury, marketing and liquidity
Treasury, grants and marketing allocations are structured to unlock initially. Treasury supports mainnet ecosystem expansion and VeryChat operations, marketing supports promotion and direct distribution, and liquidity provision supports trading conditions.
Being unlocked does not mean already spent, sold or paid. Actual execution must be checked separately against operational data and address-level records.
## Participation-based distribution is not a fixed calendar
The payout pace for node, fruit and invitation rewards varies with participant numbers, activity and reward tiers. Dates in an estimated unlock schedule should not be read as guaranteed payment dates.
App participation rewards are managed within the unified VeryChat rewards allocation. Distribution speed depends on participation, payment conditions and actual execution.
This page updates confirmed payouts and withdrawals together with their reference date. Once the listing schedule is confirmed, eligible unlock categories and amounts will be added. Scheduled unlocks will be distinguished from amounts actually paid.
**KYC withdrawals and node mining**
As of: 2026-10-08
**Total of reported categories: 1,971,048,798.367353 VERY**
The total combines KYC withdrawals and node mining. Node mining is not a measure of actual on-chain withdrawals or total circulating supply.
| KYC withdrawals and node mining | Unit: VERY |
| --- | ---: |
| VeryChat app | 776,698,747.2 |
| Nodes | 1,194,350,051.167353 |
| Team and advisors | No distribution currently planned |
| Investors and KOL | No distribution currently planned |
| Ecosystem · treasury and grants | Reporting planned |
| Marketing | Reporting planned |
| Liquidity provision (LP) | No distribution currently planned |
First KYC · 2025-08-10: 195,756,065.6 VERY
Second KYC · 2026-08-10: 580,942,681.6 VERY
Nodes use daily mining CSV records from 2024-06-04 to 2026-10-08. KYC amounts appear on confirmed withdrawal dates.
Sources: developer-provided daily node mining CSV and operating-team KYC withdrawal records. Categories without a displayed amount are excluded from the total.
---
# 8. Earn. Use. Burn. Then participate again.
Connecting contribution and use, with the 50%/20%/30% distribution and burning of ad spend.
Updated: 2026-10-07
A design connecting service use and contribution. It does not apply the same burn rate to every use.
## Earn — distribution for contribution
Early users, people inviting friends, regular participants, channel builders and network participants contribute in different ways. VERY is distributed by reward rules suited to each contribution’s purpose.
Halving lowers base rewards as participation and cumulative distribution grow. It recognizes the difficulty of building an early ecosystem while managing a defined distribution budget.
## Use — everyday and business uses
VERY can be used at supporting VeryPOS merchants and for VeryAds advertising. USDT-based transfers and payments are offered in the same product ecosystem, but a USDT payment amount is not VERY consumption.
A store can become an advertiser, and a channel operator can connect content with advertising. These are connections based on participants’ needs, not a mandatory one-way transaction sequence.
## Burn and redistribution — results of use
Some advertising VERY returns to participants and some is burned. Advertising-funded node proof rewards connect service use and network contribution in addition to the initial node-reward allocation.
Halving adjusts the pace of new rewards; burning removes part of used amounts from supply available to circulate. The mechanisms differ in purpose and trigger conditions.
## Advertising distribution and burning
### The basis is VERY actually spent on advertising
Advertisers use VERY. Amounts actually spent are distributed as below; unused top-up balances, total supply and store sales are not the basis for these percentages.
Policy confirmed 2026-09-27. Distinguish the calculation basis from the recipients.
| Recipient / use | Share | Role |
| --- | ---: | --- |
| VeryChat users and channels | 50% | Returns to content and participation |
| Node proof participants | 20% | Rewards actual network participation |
| Burning | 30% | Connects advertising use and supply management |
### Example: spending 1,000 VERY
If 1,000 VERY is actually spent on ads, 500 goes to users/channels, 200 to node proof participants and 300 to burning. The 20% is for the participant group as a whole, not 20% of ad spend for each person.
How the 50% is split among users, channel operators and other reward pools, and how node weights and settlement cycles work, require separate operating rules. This document does not invent unconfirmed percentages.
### Ad-spend distribution versus internal rewards
**50/20/30 applies to all VERY spent on advertising.** Internal channel and staking rewards are separate. Until funding and recipients are defined, no additional ratio is applied to total ad spend. See [channel staking](/whitepaper/en/channels/#channel-staking) and [policy records](/whitepaper/en/references/#policy-record) for payment conditions.
### VeryPOS payment burning is separate
The direction of burning part of VERY used for payment fees is separate from ad distribution. Without confirmed details about the fee share and burn frequency, the 30% is not carried across. It also does not mean burning 30% of the USDT payment principal.
### Policy is different from results
A burn percentage is a policy; cumulative burning is an execution result. Buybacks and burns are also different events. Figures without verified burn records, dates and sources are not labeled as on-chain verified.
## Advertising results on the website
| Metric | Meaning | Unit |
| --- | --- | --- |
| Total usage | Cumulative VERY used for ads | VERY |
| Community distribution | Amount distributed to users and channels | VERY |
| Node distribution | Advertising funds distributed to node proof participants | VERY |
| Burned VERY | Cumulative burns linked to advertising use | VERY |
| Buyback fund | Fund balance for buying back VERY | USDT |
The website shows the advertising API snapshot time and retrieval time. Failed requests preserve the last verified values and their original time. Failed refreshes do not turn values into zero or relabel old retrieval times as new.
The advertising API’s node distribution is the **node share of advertising funds**, separate from payments out of the initial 2 billion node allocation or KYC withdrawals. The buyback fund is in USDT; its balance is not added to burned VERY.
## Our belief in broader participation
We aim for more participants and VERY ownership spread across more individuals. Fruit, invitations and channel activity lead to visits and content consumption; traffic creates advertising demand and VERY use, and redistributed VERY reaches participants more widely.
This cycle is a design intention, not a formula in which burning automatically raises prices or rising prices guarantee more users. Project growth is assessed through real use and contribution.
---
# 9. Fruit harvesting rewards steady participation.
Harvest VERY every 12 hours. Seven base-reward stages, with further halvings every 400 million after 1 billion in cumulative distribution.
Updated: 2026-10-07
## Purpose of fruit rewards
Fruit harvesting is a participation reward encouraging continued visits and activity in VeryChat. Plant seeds and harvest fruit to receive VERY. Rewards can increase with your invitation-based level and the share of invited friends participating with you.
“Mining” in the app refers to this participation-reward experience. It uses different calculations from [VeryChain node rewards](/whitepaper/en/verychain/#node-rewards) for block-validation participation.
## The basic cycle is 12 hours
After planting a seed, **harvest fruit every 12 hours**. Plant again after harvesting to start the next cycle. Base rewards depend on cumulative fruit harvested and distributed across the ecosystem; your level and friend boost are then applied.
## Seven stages based on cumulative distribution
The same halving policy as the homepage. Desktop chart stages have equal horizontal widths, not widths proportional to amounts. Mobile bars compare the reward at each stage.
| Cumulative fruit harvest / distribution | Base reward per 12 hours |
| --- | ---: |
| Up to 300,000,000 VERY | 4.8 VERY |
| 300,000,001~500,000,000 VERY | 2.4 VERY |
| 500,000,001~700,000,000 VERY | 1.2 VERY |
| 700,000,001~1,000,000,000 VERY | 0.6 VERY |
| 1,000,000,001~1,400,000,000 VERY | 0.3 VERY |
| 1,400,000,001~1,800,000,000 VERY | 0.15 VERY |
| 1,800,000,001~2,200,000,000 VERY | 0.075 VERY |
**Three additional stages halve the base reward for every further 400 million VERY distributed after 1 billion.** The reward is 0.3 above 1 billion, 0.15 above 1.4 billion and 0.075 VERY above 1.8 billion.
Halving is based on cumulative harvest and distribution, not dates or how long an individual has been registered. It does not reduce wallet balances already received.
## What the current-stage marker means
The homepage marker represents **the later part of the 1.2 VERY stage, confirmed by operations on 2026-09-27**. The bright point is an approximate position near that stage’s right end. It is not a measurement of live cumulative harvesting or a forecast date for the next stage.
## Levels and items
The number of friends you invite determines your level and base-reward multiplier. An additional friend-mining boost applies **from level 3**.
Fruit reward = base reward × level multiplier × (1 + friend boost ratio)
For example, with a 1.2 VERY base reward, a level 4 multiplier of ×5, and 6 of 15 invited friends mining with you, the calculation is `1.2 × 5 × (1 + 6 ÷ 15) = 8.4 VERY`. [Invitation rewards and friend boost](/whitepaper/en/invitations/#levels-and-boost) covers all 15 levels and the calculation.
Harvest-time reduction items, boosters and events have separate terms. Their effects and temporary benefits are not added into the base halving table.
## Rewards and funding beyond 1 billion VERY
The current halving table describes **stages through 2.2 billion VERY in cumulative distribution**. These amounts are thresholds for changes in reward rates, not a separately allocated total fruit-reward budget.
The 2026-10-07 tokenomics allocates **3.4 billion VERY** to VeryChat rewards as a whole. Fruit, invitation and channel rewards are managed within this unified allocation, without separate total allocations for each. The 2.2 billion threshold does not represent an extra issuance of 2.2 billion. VERY returning to the ecosystem from advertising follows the [advertising distribution policy](/whitepaper/en/economy/#advertising-allocation).
---
# 10. Contributing by connecting new participants.
Distinguishing invitation halvings, 15 personal levels and friend-boost calculations.
Updated: 2026-10-07
## Purpose of invitation rewards
Invitations help new users join the ecosystem. Contributions are recognized more when the user base is small; the per-invitation reward decreases as registrations grow.
## Two separate effects
Direct invitation rewards and personal fruit-harvest levels are separate. A signup-driven halving of the invitation rate does not automatically halve the level table based on your invited friends.
## Halving by total registrations
Invitation halvings use **total registrations**; fruit halvings use **cumulative fruit harvested and distributed**. Current homepage invitation rates are below.
Desktop stages use equal widths; mobile bars compare rewards. The dated marker represents about 1.5 million registrations as of 2026-09-27.
| Total registrations | Reward per invitation |
| --- | ---: |
| 1–500,000 | 100 VERY |
| 500,001–2,500,000 | 50 VERY |
| 2,500,001–6,500,000 | 25 VERY |
| 6,500,001–7,000,000 | 12.5 VERY |
| 7,000,001–15,000,000 | 6.25 VERY |
| 15,000,001–31,000,000 | 3.125 VERY |
| 31,000,001–63,000,000+ | 1.56 VERY |
These rates apply to one invitation reward. Inviter and new-user eligibility and events follow app operating rules. Location-based map estimates are not used as the account database’s halving decision value.
## Scope of later stages
Rates are aligned with the seven homepage stages. Actual totals depend on reward eligibility, recipient counts and event conditions, and cannot be calculated from stage registration counts alone.
## Applying event terms
Eligibility, duration and extra invitation-event rewards follow each event’s announcement. Base halving rates remain distinct from temporary event benefits.
## 15 levels and friend boost
### Levels reflect your invitation contribution
The 15 fruit-reward levels follow below. Unlike invitation rates that change with total registrations, these are **fruit-reward multipliers based on friends you invited**.
| Level | Invited friends | Base fruit reward multiplier |
| --- | --- | ---: |
| 1 | 0 | ×1 |
| 2 | 1–5 | ×3 |
| 3 | 6–10 | ×4 |
| 4 | 11–20 | ×5 |
| 5 | 21–30 | ×6 |
| 6 | 31–50 | ×7 |
| 7 | 51–100 | ×8 |
| 8 | 101–200 | ×9 |
| 9 | 201–500 | ×10 |
| 10 | 501–1,000 | ×11 |
| 11 | 1,001–2,000 | ×12 |
| 12 | 2,001–3,000 | ×13 |
| 13 | 3,001–5,000 | ×14 |
| 14 | 5,001–10,000 | ×15 |
| 15 | 10,001+ | ×16 |
### Friend mining boost
A friend boost applies **at level 3 and above** to recognize activity with friends. The homepage calculation is:
Friend boost = friends currently mining ÷ total friends invited
A 40% boost adds 40% of the level-adjusted reward; it does not reduce the total to 40%. No division is needed for level 1 with no invitees or other ineligible levels.
The denominator is the number of friends you invited. Confirm boost in the app using eligible friends and actual mining participation.
### Example totaling 33.6 VERY
Assume a 4.8 VERY base reward, level 4’s ×5, 15 invited friends, and 6 mining with you.
| Calculation | Formula | Result |
| --- | --- | ---: |
| Apply level | 4.8 × 5 | 24 VERY |
| Friend boost ratio | 6 ÷ 15 | 40% |
| Extra reward | 24 × 0.4 | 9.6 VERY |
| Total reward | 24 + 9.6 | **33.6 VERY** |
4.8 × 5 × (1 + 6 ÷ 15) = 33.6 VERY
The total combines the level-adjusted base and added friend boost. `4.8 × 5 × 40%` calculates only the extra 9.6 VERY; add the 24 VERY base for the total.
### What changes after a halving?
Even with the same level and friend ratio, a different base changes the result. At a 1.2 VERY base under the same conditions, `1.2 × 5 × 1.4 = 8.4 VERY`. This explains the formula, not a query of anyone’s current payout.
Harvest-time items and event benefits follow separate terms and are excluded from this example.
---
# 11. Channels that turn connections into communities
Channel use, content recommendations, and channel rewards and staking that have not yet launched.
Updated: 2026-10-07
## What is a channel?
A channel is a social community where operators publish content and subscribers read and participate. Personal interests, local groups, brands, and shop news bring people together. Group chats focus on conversation among members; channels focus on publishing, subscribing, and discovery.
The initial limit is **200,000 subscribers per channel** and **10,000 participants per group chat**. Expanding channel capacity is a stated direction, not a guarantee of unlimited channels today.
## Using a channel
Browse new channels and popular content, then subscribe to channels that interest you. Read posts, leave comments and reactions, and understand conversations in other languages with [on-device AI translation](/whitepaper/en/verychat/#on-device-ai). Channels are available on mobile and desktop.
Publishing and viewing content create community activity, and active channels become placements where advertisers reach users. **Channel rewards have not launched.** The subscription rewards and staking below are pre-launch designs; launch dates and final payout conditions will be announced separately.
## Roles of operators and members
| Role or feature | Description |
| --- | --- |
| Channel owner | Manages the channel and grants operating permissions. Only the owner can delete the channel. |
| Co-administrator | Helps manage posts and the community within permissions set by the owner. |
| Member levels | Allow different permissions for different participants. |
| Pinned announcements | Keep important content at the top. |
| Notify everyone | `@everyone` is based on one use per day. Delivery also depends on the device's notification permissions. |
| Linked group chat | Connects published channel content with conversations among members. |
## Content discovery across languages
Channels are discovered through interests and participation signals. Popular content introduces channels to new users, while [on-device translation](/whitepaper/en/verychat/#on-device-ai) helps them understand content from other language communities.
Exposure is not described as depending only on subscriber counts. The [recommendation structure](/whitepaper/en/channels/#content-recommendations) considers post reactions, content relevance, and user interests together.
## Community economic activity
Operators can airdrop assets from their own wallets to members. Participation conditions based on token or NFT holdings, and staking in a subscribed channel, also connect community economic activity. Follow the in-app guidance for each feature's actual availability and conditions.
Channel rewards follow [subscription-based rewards](/whitepaper/en/channels/#subscription-rewards), advertising participation follows [ad-spend distribution](/whitepaper/en/economy/#advertising-allocation), and staking follows a [separate policy](/whitepaper/en/channels/#channel-staking). Subscribing to or operating a channel does not automatically create every type of reward.
## Popular posts and recommendations
### Popularity and relevance together
VeryChat recommendations consider both widely engaging content and content relevant to each user. The structure combines **engagement E**, **content matching M**, and **user interest U**.
The formulas below are published conceptual descriptions of the recommendation score. Operational weights, normalization, and measurement periods are not public. These illustrations are not production code or a reproducible ranking calculator.
### 1. Engagement E
Reflects people's reactions to a post.
```text
E = wₑ₁ × LI + wₑ₂ × V + wₑ₃ × S
```
| Symbol | Meaning |
| --- | --- |
| LI | Likes |
| V | Views |
| S | Shares |
| wₑ₁, wₑ₂, wₑ₃ | Weights for each reaction |
Views, likes, and shares are combined as different signals, not treated as identical. This public formula alone does not reveal points per reaction or the time window for counting views.
### 2. Content matching M
Reflects how relevant the content is to the user's interests.
```text
M = wₘ₁ × K + wₘ₂ × D + wₘ₃ × C
```
| Symbol | Meaning |
| --- | --- |
| K | Match between keywords and interests |
| D | Relevance and quality of the content description |
| C | Relevance to topics and trends |
| wₘ₁, wₘ₂, wₘ₃ | Weights for each content signal |
More text or repeated keywords do not guarantee exposure. These are signals used to evaluate relevance.
### 3. User interest U
Reflects that different people may have different interests in the same post.
```text
U = wᵤ₁ × H + wᵤ₂ × SU + wᵤ₃ × A
```
| Symbol | Meaning |
| --- | --- |
| H | Viewing history |
| SU | Subscribed channels |
| A | Interest signals from conversations, likes, and other activity |
| wᵤ₁, wᵤ₂, wᵤ₃ | Weights for each user signal |
### 4. Final recommendation score R
```text
R = w₁ × E + w₂ × M + w₃ × U
```
Combining engagement, content matching, and user interest determines exposure priority conceptually. Recommendations are designed to help new users and communities in other languages discover channel content.
### Public information and reward calculations
Recommendation scores support content discovery and are **not a direct formula for VERY payouts**. Channel reward eligibility and actual payouts follow separate policies.
Published material does not currently specify weight values, duplicate-view handling, time decay, fraud-filter thresholds, or model versions. This document does not invent them. If operational rules are published, their version and effective date should also be recorded.
## Channel subscription rewards — not yet launched
**Channel subscription rewards have not launched.** The following is a pre-launch design, not rewards currently being paid or confirmed amounts receivable.
### Eligibility and reward design
For **channels with at least 100 subscribers**, the design has two stages based on total subscriptions across all channels.
| Total subscriptions across channels | Proposed monthly reward |
| --- | --- |
| Below 10 million | 1 VERY per subscriber of the channel |
| 10 million or more | 10 million VERY per month, allocated by each channel's share of subscriptions |
The second stage uses the following structure.
```text
Monthly channel reward = 10,000,000 VERY × channel subscriptions ÷ total subscriptions across all channels
```
For example, 20 million total subscriptions and 10,000 for one channel produce 5,000 VERY per month under this formula. This only illustrates the calculation, not a confirmed payout satisfying activity assessments and payment requirements.
### Subscriptions are not unique people
One person may subscribe to multiple channels, so total subscriptions differ from unique users. Whether ineligible channels enter the denominator and when subscriptions are measured still require confirmation through operating policy.
### Real activity matters more than inflated counts
Channel activity is assessed through signals such as:
- Whether content is updated consistently
- Genuine participation through views, conversations, and reactions
- Whether subscriber behavior is natural
- Long inactivity, fraudulent participation, or confirmed reports
Behavior analysis and AI are proposed directions; this does not mean a particular model is already operating or automatic decisions are perfect. Detailed assessment thresholds are not public.
## Channel staking — not yet launched
### Choose a community you subscribe to
Channel staking rewards have **not yet launched** either. The design lets users stake VERY in a subscribed channel and share rewards between the operator and participants.
> This chapter describes the channel staking design. Funding details connected to the latest ad-allocation policy, locking and unlocking conditions, and current applicability require further confirmation.
### Distribution within a channel
The proposed channel reward pool is split 20% to the operator / 80% to staking participants. Channel owners may also stake.
With reward pool Q, a user's stake s, and total eligible stake S, proportional distribution is based on `Q × s / S`. This describes the ratio when the same distribution period and eligibility conditions apply.
### Different from ad-spend allocation
The current VeryAds allocation is 50% to users and channels, 20% to node proof, and 30% burned. The operator 20% / participant 80% split above is internal to the channel pool, not an extra allocation of all ad spend.
Expected yields are not calculated while the amount earmarked for staking from the users-and-channels 50% share remains undecided.
### Rules to finalize before publication
- Payout period, eligibility, and snapshot time
- Lock period, early unlocking, and unpaid rewards
- Whether changing stake balances receive time weighting
- How reward funding connects to advertising funds
- Handling user assets and rewards when a channel closes or is sanctioned
Staking yield depends on funding, duration, and total stake. No fixed APY is confirmed. Calculation examples will be updated after actual payout conditions are verified.
---
# 12. VeryChain connects participation
VeryChain, node NFTs and rewards, plus client downloads, installation, synchronization, and operation.
Updated: 2026-10-08
## Connecting services and the network
VeryChain is VERY's network foundation. **VeryNetwork** names the ecosystem of people, services, and economic activity; **VeryChain** names the blockchain. “Mainnet” means this chain's live operating network.
Users participate in VeryChat, developers connect services, and node participants receive rewards for network contributions under defined policies. These roles connect, but harvesting fruit in the app is not described as block production.
## EVM compatibility
VeryChain is an **EVM-compatible mainnet**. It uses VERY as its native coin and supports development with Solidity smart contracts and Ethereum tools. Check client and compiler compatibility for the specific release.
EVM executes smart contracts. Accounts sign transactions with keys, and nodes process transactions and state changes. Gas used and gas price are different values; `gas used × gas price` is the basic network-fee calculation.
## Public network information
Use these settings to connect a wallet or developer tool to VERY Mainnet.
| Item | Setting |
| --- | --- |
| Network name | `VERY Mainnet` |
| Network type | EVM-compatible mainnet |
| Chain ID — decimal | `4613` |
| Chain ID — HEX | `0x1205` |
| RPC URL | `https://rpc.verylabs.io` |
| Currency symbol / native coin | `VERY` |
| Block explorer | VERY scan — [https://veryscan.io](https://veryscan.io) |
4613 and 0x1205 express the same Chain ID in decimal and hexadecimal. Use `4613` when a wallet requests a regular number, or `0x1205` when a developer tool requests HEX. Mainnet transaction fees use the native coin VERY.
### Add the network to a wallet manually
1. In a wallet supporting custom EVM networks, open Add network or Add manually. Menu names may vary by wallet.
2. Enter the network name, RPC URL, Chain ID, currency symbol, and explorer address from the table.
3. Save and confirm that VERY Mainnet is selected. Look up sent transactions on VERY scan by transaction hash.
Adding a network sets the wallet's connection target; it does not move assets from another chain to VERY Mainnet. See the [developer guide](/whitepaper/en/developers/#rpc-연결-확인) for querying the RPC Chain ID.
## Consensus and node-proof rewards
The website describes **client operation and network verification participation by node NFT holders**. NFT allocation, actual operation, and valid proof participation have distinct roles in rewards. Holding an NFT differs from running a client and submitting valid proof.
This chapter covers [node allocation and rewards](#node-rewards) and [client downloads and operation](#node-operation). App fruit harvesting and network node proof are different forms of participation.
## Node allocation and rewards
### How are nodes distributed?
There are **8,000 node NFTs** in total. After the initial sale of 1,600, distribution focuses on people inviting friends and contributing to ecosystem growth. This links node participation to VeryChat's growth and the mainnet ecosystem.
| Allocation | Quantity | Share |
| --- | ---: | ---: |
| Invitation contributions | 4,800 | 60% |
| Ecosystem contributions | 1,600 | 20% |
| Initial sale | 1,600 | 20% |
The table does not guarantee immediate distribution at a specific invitation count. Eligibility selection and timing follow official program announcements.
### Base rewards and node proof
A total of **2 billion VERY** is allocated to node rewards. Base rewards are proportional to total distributed node NFTs and individual holdings.
```text
Daily base reward = 864,000 VERY ÷ distributed node NFTs × NFTs held
```
Node rewards follow the same halving schedule as fruit rewards in the VeryChat app.
Qualifying node-proof participation adds **100% of the base reward**, producing **twice** the base-only amount. Additional funding or separately applicable rewards may change the total. The daily base reward is not the same as the full daily payout including all extras.
Average per NFT, base mining amount, and additional proof reward are distinct metrics. [Network status](https://verylabs.io/en/network/) presents them from the same snapshot. Check the app for your confirmed withdrawable reward.
### Rewards connected to VeryAds
**20% of VERY used in VeryAds goes to node-proof participants.** This is not described as equal payments to every NFT holder. Eligibility, proof records, and allocation criteria for each period follow the applicable reward policy.
Ad distribution is funded by actual advertising use and must be measured separately from the initial 2 billion VERY node reward allocation.
### Initial-sale referrals and remaining allocation
Initial-sale referral rewards are 5% per NFT, up to 100% extra. Do not interpret this as ongoing new-purchase referrals after that sale ended; existing participants should check operating notices for applicable conditions.
The website calculates cumulative node payouts as `2,000,000,000 VERY − remaining mining amount`. This is policy-based payout reporting, not identical to a single figure directly proven by a block explorer. Check the dates and definitions of the reward pool, paid amounts, and remainder together.
## Node status and withdrawal reporting
The public status API provides remaining mining amounts, averages per NFT, base amounts, and proof rewards. The website shows retrieval time and data status, retaining the last valid values during temporary failures.
Read cumulative payments calculated by `2,000,000,000 VERY − remaining mining amount` alongside [KYC and node withdrawal reports](/whitepaper/en/ecosystem/#온체인으로-출금된-very) using matching reference dates. The 20% node share from advertising is shown as a separate source.
## Running and operating a node
For your first installation, follow Preparation → instructions for your environment → check synchronization. Expand only one environment: Mac, Windows, or cloud. The node downloads VeryChain blocks and follows the latest state. This is called synchronization.
Use Mac or Windows if your computer can stay on. Cloud operation rents a server: the node keeps running when your computer is off, but server, storage, and management costs apply.
### Preparation and client downloads
- Computer or server: CPU with at least 4 cores, 8 GB RAM, and 500 GB storage (SSD recommended). Check free space as synchronized data grows.
- Internet and power: Keep both connected during installation, synchronization, and operation. Check sleep and automatic shutdown settings.
- Node-specific key: Confirm your node NFT and eligibility, complete KYC, and obtain the key through the official process. If you do not have one, check issuance first.
| Environment | Download | File |
| --- | --- | --- |
| Apple Silicon Mac | [Mac node client ZIP](https://family-assets.verycloud.io/nodes/2026-10-08/a5819881e716/2026_VeryNode_Client_for_Mac.zip) | `2026_VeryNode_Client_for_Mac.zip` |
| Windows x64 | [Windows node client ZIP](https://family-assets.verycloud.io/nodes/2026-10-08/4fcc0d92bddf/2026_VeryNode_Client_for_Windows.zip) | `2026_VeryNode_Client_for_Windows.zip` |
| Ubuntu server | [Cloud installation ZIP](https://family-assets.verycloud.io/nodes/2026-10-08/3f30851effa6/2026_Guide.zip) | `2026_Guide.zip` |
These files are node operating programs, not the VeryChat desktop messenger. Instructions follow the 2026 packages; screenshots come from the earlier installation guide. Buttons may vary by OS version. Click an image to enlarge it in a new tab.
### Set the node-specific key
The node-specific key identifies whose participation the node represents and links to the registered VERY distribution wallet. Do not substitute a wallet private key or recovery phrase. It also differs from the `.pem` file used to access a cloud server.
Open `key.json` in the installation files. Replace only the example text inside quotation marks with your issued node key. Keep `key`, braces, colon, and quotation marks unchanged.
```json
{
"key": "YOUR_ISSUED_NODE_KEY"
}
```
Mac and Windows use `key.json` inside `src`; cloud uses `key.json` inside `2026_Guide`. Opening and saving steps are below for each environment. Never share the key or screenshots revealing it.
MAC · 5 STEPSStart a node on MacFrom extraction and execution permission to synchronization
### Run on macOS
For Apple Silicon Macs (M1 or later). Check the chip under the Apple menu → About This Mac. An Intel Mac package is not included in this guide.
#### 1. Download and extract
Click Mac node client ZIP above, then open Finder's Downloads folder. Double-click the ZIP to extract it and keep the resulting folder somewhere easy to find.
The current package contains the following two items. Keep `very` together with the `src` folder, rather than moving the program alone to the desktop.
```text
Extracted folder/
├── very ← program to run
└── src/
└── key.json ← file for the node-specific key
```
Before continuing: Finder should show both very and src. The separate client file shown in older instructions is not required in the current package.
#### 2. Open key.json and save your key
1. Open the `src` folder and find `key.json`.
2. Right-click → Open With → TextEdit. If it is hard to find, switch Finder to list view.
3. Delete only the example text such as `Paste a private key here` and paste your node key between the quotation marks. Check for accidental spaces or line breaks around it.
4. Save with Command (⌘)+S. Keep the name `key.json`; do not save a new `.txt` or `.rtf` file.
Replace only the blue-selected example with your real node key. The text shown is not a real key. Enlarge ↗
#### 3. Run very
Go back to the parent folder of `src` and double-click `very`. If the program opens, skip to step 5. If macOS blocks an unidentified developer, close the dialog and continue to step 4.
If this appears, allow this specific program in System Settings. Enlarge ↗
#### 4. Allow execution in macOS
1. Open Apple menu → System Settings → Privacy & Security.
2. Find the notice that `very` was blocked and click Open Anyway. You may need to attempt running `very` first for this to appear.
3. Authenticate with your Mac password or Touch ID, then choose Open in the confirmation. Run `very` again from Finder if needed.
The red border marks Open Anyway. Layout may differ by macOS version. Enlarge ↗Confirm the program name is very, then click Open. Enlarge ↗
Use this procedure only for a developer verification warning on the official files linked here. If malware or file damage is detected, do not force execution; verify the file and source. [Apple's app-opening guide](https://support.apple.com/en-us/102445) describes the same settings path.
#### 5. Check synchronization logs and leave it running
The window continuously shows times and English messages. These are the node's logs, or activity records. `Block synchronisation started` means block data download has begun.
The red border marks synchronization starting. Dates and block numbers are from an earlier example. Enlarge ↗
After installation: Check that number=... changes, then continue to “Verify synchronization and proof participation” below. A start message does not mean synchronization is complete.
Keep the program window and internet connection active. Sleeping the Mac or closing a laptop lid can interrupt operation. Connect power and check battery or energy sleep settings. A dark screen is different from a sleeping computer.
[Check synchronization completion](#동기화-완료와-증명-참여-확인)
WINDOWS · 5 STEPSStart a node on WindowsPrepare folders, edit with Notepad, and run as administrator
### Run on Windows
For Intel or AMD x64 PCs running Windows 11. Check System type under Settings → System → About.
#### 1. Download and extract to a dedicated folder
Download the Windows node client ZIP. In Downloads, right-click it → Extract All. A folder such as `very_node` on your desktop makes it easy to find.
Do not run inside the ZIP. The extracted folder must contain both `very.exe` and `src`.
```text
very_node/
├── very.exe ← program to run
└── src/
└── key.json ← file for the node-specific key
```
Enable View → Show → File name extensions in Explorer to see `.exe` and `.json`.
#### 2. Open key.json in Notepad
Open `src`, right-click `key.json` → Edit in Notepad. If missing, choose Open with → Notepad.
Use this to locate key.json. Other files in the older screenshot may differ from today's package. Enlarge ↗
#### 3. Enter and save the key
Replace only the example inside quotation marks and save with Ctrl+S. Close Notepad and confirm the name remains `key.json`. A file named `key.json.txt` may not be read by the node.
Keep the quotation marks; replace only the selected text. Enlarge ↗
#### 4. Run as administrator
Return to the parent folder of `src`, then right-click `very.exe` → Run as administrator. If Windows asks permission to make changes, verify the file before allowing it.
Explorer may display the name as very or very.exe depending on settings. Enlarge ↗
SmartScreen may show “Windows protected your PC.” Once you verify this is the official file linked here, choose More info → Run anyway, or Run if already visible. If security software detects or quarantines malware, treat that separately and investigate the block first.
Example Run button location. Colors and buttons vary by Windows version and security policy. Enlarge ↗
#### 5. Check synchronization starting in the logs
The program shows English logs. `Block synchronisation started` means synchronization has begun. The initial block download can take time.
Check the red-bordered message, then confirm block numbers keep updating. This screenshot is from a past run. Enlarge ↗
After installation: Keep the window open and continue to synchronization and proof verification below. Closing the window or shutting down the PC stops the node.
For continuous operation, check power and sleep settings. After restarting Windows, run `very.exe` from the same folder and confirm logs resume.
[Check synchronization completion](#동기화-완료와-증명-참여-확인)
CLOUD · 8 STEPSStart a node on a cloud serverCreate an AWS server, connect to Ubuntu, and operate the node
### Run in the cloud — Ubuntu
Cloud means renting an internet-connected computer. This example creates an Ubuntu server on AWS EC2. If you already have Ubuntu, start at step 3 after checking specifications, access keys, and network settings.
There are two command windows: “On your computer” means Mac Terminal or Windows PowerShell; “On the server” means the SSH session. Run one line at a time and check the result before continuing.
#### 1. Open EC2 in AWS
Sign in to AWS Console, choose your region (server location), and search for EC2 at the top.
Choose EC2 from search results. This is an earlier console example. Enlarge ↗
Open Instances in the left menu, then Launch instances. An instance is one server you create.
Start creating a server with the orange button at top right. Enlarge ↗
#### 2. Set specifications, access keys, and networking
Work down the settings form. Use the specifications in the table below, rather than older defaults shown in screenshots.
| Setting | Selection |
| --- | --- |
| Name | Something memorable, such as `very-node` |
| Operating system (AMI) | Ubuntu Server 24.04 LTS or 22.04 LTS, 64-bit x86 |
| Instance type | At least 4 vCPUs and 8 GiB RAM |
| Key pair | Create a new key pair → e.g. `very-node-key` → RSA → download as `.pem` |
| Auto-assign public IP | Enable |
| Storage | At least 500 GiB SSD; monitor usage during operation |
The key pair lets you access the server. Store the downloaded `very-node-key.pem` somewhere safe and findable. Do not put this file in `key.json`.
A security group defines incoming connections. Create or edit a group with these inbound rules.
| Purpose | Protocol / port | Allowed source |
| --- | --- | --- |
| Server administration (SSH) | TCP / 22 | My IP; only the administrator's public IP |
| Node connections | TCP / 30303 | IPv4 `0.0.0.0/0` |
| Node discovery | UDP / 30303 | IPv4 `0.0.0.0/0` |
SSH's My IP restriction and allowing all IPv4 for node traffic are separate rules. This package does not require exposing extra RPC or administrative ports. Outbound internet access must also work.
Example key-pair and network settings. Apply the rules above instead of copying the screenshot's old security group. Enlarge ↗
Set storage to at least 500 GiB and review the summary. Check estimated server and disk costs before launching. Do not assume this specification is free-tier eligible.
Confirm storage before launching. Pricing and free-tier notes in the screenshot are not current rates. Enlarge ↗
Before continuing: Check the instance is Running and has passed status checks. Allow preparation time after launch.
#### 3. Find the server IP and prepare installation files
Select your instance and copy Public IPv4 address from its details. Replace `YOUR_SERVER_IP` in the commands with it. Do not copy the obscured address in the screenshot.
Use the public IPv4, not the private IP used only inside the server network. Enlarge ↗
For a connection example specific to your server, select the instance and open Connect → SSH client.
Connect shows access methods. The following steps use your computer's SSH client. Enlarge ↗
Place these two files in your computer's Downloads folder.
- `2026_Guide.zip` from the download table above
- `very-node-key.pem` from server creation
If you chose other filenames, use those names in the commands. This guide uses AWS Ubuntu's default username, `ubuntu`.
#### 4. Transfer files and connect from your computer
On Mac: Open Terminal using Command (⌘)+Space. Replace `YOUR_SERVER_IP` with your address and run one line at a time. `chmod 400` makes the server key readable only by you.
```sh
cd ~/Downloads
chmod 400 very-node-key.pem
scp -i very-node-key.pem 2026_Guide.zip ubuntu@YOUR_SERVER_IP:/home/ubuntu/
ssh -i very-node-key.pem ubuntu@YOUR_SERVER_IP
```
On Windows: Search PowerShell in Start. If Downloads is elsewhere, change the first line to your folder path.
```powershell
cd "$HOME\Downloads"
scp -i .\very-node-key.pem .\2026_Guide.zip ubuntu@YOUR_SERVER_IP:/home/ubuntu/
ssh -i .\very-node-key.pem ubuntu@YOUR_SERVER_IP
```
`scp` copies the ZIP to the server; `ssh` connects. On first connection you may see `yes/no`. Verify your server address and, if possible, compare its fingerprint in AWS Console before entering `yes`. For key permission or connection errors, see [AWS SSH guidance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-ssh.html).
If Windows cannot find `ssh` or `scp`, install the OpenSSH client using the Windows steps in the AWS guide, then reopen PowerShell and connect.
You are now on the server: A prompt like ubuntu@... confirms connection. Run steps 5–8 in this window.
#### 5. Extract on the server and enter the node key
Prepare the required tools and extract the ZIP. Run each line and continue only if no error occurs.
```sh
cd /home/ubuntu
sudo apt-get update
sudo apt-get install -y unzip nano
unzip 2026_Guide.zip
cd 2026_Guide
ls
```
`ls` lists files in the current folder. You are in the right location if the following files appear.
```text
2026_Guide/
├── 0_prepare.sh
├── 1_build.sh
├── 2_execute.sh
├── 3_log.sh
├── docker-compose.yml
└── key.json
```
Open the key file with this command.
```sh
nano key.json
```
`nano` is a server text editor. Use arrow keys, remove only the sample between quotation marks, and paste your issued node key. Save with Ctrl+O → Enter, then close with Ctrl+X. On Mac these use Control, not Command.
The cloud key file belongs in this folder. Do not create a `src` folder like on Mac or Windows. `docker-compose.yml` and `key.json` must sit together.
#### 6. Install Docker and reconnect
Docker runs the node in a defined environment. Run the following in the same folder; the package script prepares Docker and Compose.
```sh
sh 0_prepare.sh
```
Wait until installation finishes and the prompt returns. If there is an error, investigate before continuing. The script also grants Docker access, so disconnect and reconnect to the server.
```sh
exit
```
You are back in your computer's command window. Reconnect using the SSH command from step 4.
```sh
ssh -i very-node-key.pem ubuntu@YOUR_SERVER_IP
```
After reconnecting to the server, enter the installation folder and check Docker with the following commands.
```sh
cd /home/ubuntu/2026_Guide
docker compose version
docker ps
```
Before continuing: A Compose version and docker ps output without permission errors mean you are ready. An empty list is fine: the node has not started yet.
#### 7. Download the node → run → view logs
Run the three commands in order, one line at a time. Wait for each to finish and check for errors.
Download the node program image. When complete, run the next command.
```sh
sh 1_build.sh
```
Start the node in the background.
```sh
sh 2_execute.sh
```
Open the logs to check operation.
```sh
sh 3_log.sh
```
Example of synchronization starting and blocks arriving. Current container names may differ; the block numbers are historical. Enlarge ↗
Check block logs keep updating after `Block synchronisation started`. Ctrl+C exits the log view only; the node keeps running in the background. Ending SSH with `exit` also leaves it running while the server and container remain active.
#### 8. Reconnect later to check status
Connect from your computer with the step 4 SSH command, then run these on the server.
```sh
cd /home/ubuntu/2026_Guide
docker compose ps
```
If `very-node` shows `Up` or `running`, the container is running. This is program status; verify synchronization separately using log block heights.
| Task | Command in the installation folder |
| --- | --- |
| View logs again | `sh 3_log.sh` — exit with Ctrl+C |
| Restart node | `docker compose restart very-node` |
| Temporarily stop | `docker compose stop very-node` |
| Start a stopped node | `docker compose start very-node` |
| Check disk space | `df -h` — check Use% and Avail |
Synchronization data is stored in `db-data/node`. Restarting does not require deleting it or `key.json`. If the server was stopped and restarted, check whether the public IP changed. Stopping only the node process does not stop all cloud charges.
[Check synchronization completion](#동기화-완료와-증명-참여-확인)
### Verify synchronization and proof participation
After starting the program, distinguish these three checks.
| Stage | What to look for | Meaning |
| --- | --- | --- |
| Running | Logs in the window or container status `Up` | Program is running |
| Synchronization started | `Block synchronisation started` | Block download has begun |
| Following latest blocks | `number=...` keeps updating toward the latest block height | Checks whether the node follows the network |
1. In a block-processing message such as `Imported new chain segment`, find `number=...`. This is the block currently processed.
2. Open [VeryScan](https://veryscan.io) and compare the current latest block, not the old screenshot's number.
3. The initial gap may be large. Leave the node running and check that it catches up over time and continues following new blocks afterward.
Synchronization time depends on internet speed, disk performance, and data volume. A brief quiet log does not justify deleting files or reinstalling from scratch.
After synchronization, node eligibility and valid proof conditions must still be met for proof rewards. An open program window does not confirm a reward. See [node allocation and rewards](#node-rewards).
### If operation or synchronization stops
Expand your situation below. After resolving it, restart the node and check that block numbers update.
The key is entered but the node fails or reports a key error
- Confirm it is the node-specific key, not a server `.pem` file or wallet recovery phrase.
- Check `src/key.json` on Mac and Windows, or `2026_Guide/key.json` in the cloud.
- Check the file is not named `key.json.txt` and that quotes, braces, and colon remain. Do not add line breaks or extra spaces inside the key.
- Save and restart an already running node. When requesting help, hide the entire key value.Windows Security blocked or deleted the file
In Windows Security → Virus & threat protection → Protection history, check the file and reason. Verify the official source and whether it is a real detection; seek support if needed. Do not restore or allow unverified files.
Only if official support confirms a false positive requiring an exception, use Virus & threat protection settings → Manage settings → Add or remove exclusions → Add an exclusion → Folder, limited to this node folder. Do not disable all Windows protection or exclude the entire Downloads folder.
Cloud connection fails or shows Permission denied
For a `ssh` connection error, check server state, public IP, username `ubuntu`, and the `.pem` file selected at creation. Also verify My IP in the SSH port 22 rule matches your current public IP, which may change when your internet connection changes.
For a Docker socket permission error in `docker ps` or a node script, confirm `0_prepare.sh` completed, run `exit`, then reconnect by SSH. New permissions apply after reconnection.
If `No such file or directory` appears, check the filename and current folder. Your computer needs the ZIP and `.pem`; on the server, switch to `cd /home/ubuntu/2026_Guide` before running scripts.
Logs stop or block numbers remain behind
1. Check that the PC is awake and the internet is connected.
2. Check available disk space; use `df -h` in the cloud.
3. In the cloud, use `docker compose ps` for status and `sh 3_log.sh` for errors. Also check TCP and UDP port 30303 for node communication.
4. Look at recurring errors and changes in block numbers together, not just one log line. Distinguish temporary warnings from persistent failures.
5. Restart after resolving the cause. Do not immediately delete existing synchronization data.
What should I send if it still does not work?
Send official node support your environment (Mac, Windows, or cloud), OS version, the step that failed, error text, and recent logs. Find support through the [official VeryNetwork channels](/whitepaper/en/linktree/).
Ensure logs and screenshots exclude node keys, wallet recovery phrases, and `.pem` contents. Sending the error and surrounding logs is enough to help identify the issue.
Sources for this chapter:
- https://verylabs.io/node
---
# 13. An ecosystem expanded by its people
Community, ecosystem support, and a roadmap and team grounded in today’s products.
Updated: 2026-10-07
## Community is where use begins
VERY’s expansion is about more than app-install counts. People invite friends, organize local gatherings, introduce stores and share how to use the services. Communities and merchants connect the digital network to everyday relationships.
Event photos on the website record this participation. Local events are identified as user-organized, except those marked as official Meetups in Korea. An event record does not establish every attendee’s reward eligibility or official representative status.
## A record of gatherings on the website
| Date | Event | Type |
| --- | --- | --- |
| 2026-08-26 | Seoul community meetup | Official event |
| 2026-06-26 | University of Uyo meetup, Nigeria | User-organized event |
| 2026-04-04 | Ngawi meetup, Indonesia | User-organized event |
| 2025-11-02 | Accra gathering, Ghana | User-organized event |
See event photos and dates in the [community albums](https://verylabs.io/en/community/). The service websites offer Korean, English, Japanese, Bengali and Indonesian to improve accessibility. Website languages and app translation languages are separate sets.
## How growth metrics are defined
The website’s **147 countries and territories** refers to the origins of users who completed the first or second KYC round. Its basis differs from the number of countries in the registered-user distribution.
User distribution is an **estimate** that sums city-location aggregates from access logs by country code. The headline rounds the full map total down to the nearest 10,000; it differs from account-database counts of registered, active and withdrawn users. The map does not reveal individuals’ live locations. Merchant-map locations are registered stores, not a promise that every payment method works at every store.
## Support for developers and businesses
Ecosystem support focuses on advertising and development so services can reach users and operate sustainably.
| Support type | What it provides |
| --- | --- |
| Advertising | VERY credits usable within the ad system, distinct from withdrawable cash or freely circulating VERY. |
| Research and development | Support based on approved development activity and evidence of expenses. |
| Ecosystem connections | Connect service use through VeryChat users, VeryAds advertising and the network. |
Selection for support does not create unlimited advertising or fixed income. Eligibility, evaluation and support amounts follow each program’s announcement.
## The expansion we aim for
We connect what people actually do rather than simply list more apps: from conversation to transfers, store payments to sales management, and business advertising to community. These connections guide ecosystem expansion.
## Roadmap
### Product experiences available today
The website review centers on VeryChat conversations, channels and participation rewards; VeryWallet profile transfers; VeryPOS stablecoin payments and store management; and VeryAds VERY-based advertising. Each product chapter explains supported networks and usage conditions.
### Directions for the next expansion
| Direction | Goal | Documented status |
| --- | --- | --- |
| VeryAds purchase and top-up | Buy VERY and fund advertising in the advertiser interface | Planned |
| VeryAds MCP | Connect AI banner creation and campaign registration | Planned |
| Integrated payments and store management | One workflow for blockchain, cash and local payment methods | Expansion direction |
| On-device AI | Improve translation and expand to uses such as summaries | Additional features such as summaries are planned |
Schedules, supported countries and release scope are updated through official product announcements.
### Broadening participation
Channel subscription and staking rewards have not launched. Designs connecting community activity and content contributions to rewards are being considered; criteria and launch timing will be announced separately. We improve products and support together so local communities, merchants and advertisers can keep using the services.
The roadmap does not guarantee fixed release dates. It distinguishes available features from development directions; releases and policy changes trigger updates to this document and the relevant product guidance.
## Team
VERY LABS builds products connecting services and blockchain. At GWDC in September 2026, founder Kwanghyun Ko described approaching global payments through the familiar messenger experience.
The project brings together business and global community, product planning and design, backend and frontend, blockchain and AI capabilities. Members’ current roles and backgrounds are updated against verified information and dates.
| Area | Main role |
| --- | --- |
| Business and global community | Service direction, partnerships, local community and user communication |
| Product planning and design | User flows, UI/UX and consistent experiences across products |
| Service development | Backend/frontend development and operations for chat, advertising and payments |
| Blockchain | VeryChain, node clients and network integration |
| AI | On-device translation and AI-powered features |
Sources for this chapter:
- https://www.tokenpost.kr/news/insights/416214
---
# 14. Trust within a familiar experience
Profile transfers, wallet recovery, KYC, on-device translation and the scope of public data.
Updated: 2026-10-08
## Using accounts and wallets safely
Your VeryChat account provides access to conversations and profiles; VeryWallet private keys and recovery information provide access to assets. **The company does not hold wallet private keys.** Do not share your PIN or recovery information. Check the app’s official recovery procedure before changing devices.
Profile transfers reduce address entry, but still require checking the recipient. Confirm the recipient, asset and amount before sending; for payments, also check the store name and order. Account recovery and wallet recovery are separate processes.
## Purpose and scope of KYC
KYC verifies identity and eligibility for specific features. Follow the app’s current guidance on supported countries, documents and verification methods. Consult the applicable privacy policy for collected information, processors, retention periods and deletion procedures.
The website reports VERY withdrawals through the first and second KYC rounds. Participant counts and withdrawal amounts are records at each report’s reference time; they are not total registrations or current active-user counts.
## Verification is different from a guarantee
Identity verification helps reduce duplicate or fraudulent participation. A counterparty completing KYC does not guarantee every transaction’s trustworthiness. Check official app and service addresses; never enter a PIN, private key or recovery information through impersonator accounts or external links.
## Wallets and privacy
On-device AI **processes translation on the device**. This is distinct from data processing for other functions, such as account login and sending or receiving messages.
The user-distribution map shows city- and country-level aggregates, not individuals’ real-time locations. The merchant map provides information about publicly registered stores.
## Support and inquiries
Login issues, account recovery, wallet recovery and transfer or payment errors have different causes and procedures. Consult [VeryChat support](https://verychat.io/en/support/) for the official steps for the relevant feature. Provide the transaction details needed for your inquiry, but never send private keys or recovery phrases.
## Nature of this document
This whitepaper explains product experiences and the economic structure. App use and personal-data processing follow each service’s current policies. Demo balances and calculation examples are presented separately from actual campaign and withdrawal statistics.
The whitepaper’s [disclaimer](/whitepaper/en/references/#disclaimer) is in Terms, policies and document history.
---
# 15. VeryChain developer guide
EVM development, network connections, contract deployment and operations, and use of public status data.
Updated: 2026-10-08
## Connecting to the network
VeryChain is an EVM-compatible mainnet. Its network name is `VERY Mainnet`, Chain ID `4613` (HEX `0x1205`), RPC URL `https://rpc.verylabs.io`, and native coin `VERY`.
Complete wallet settings are listed in [VeryChain public network information](/whitepaper/en/verychain/#공개-네트워크-정보). View blocks and transactions on [VERY scan](https://veryscan.io).
### Checking the RPC connection
In your development environment, the following read-only request checks the Chain ID returned by the RPC. It runs without a connected wallet or private key and does not send a transaction.
```sh
curl --request POST 'https://rpc.verylabs.io' \
--header 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
```
The expected `result` value is `0x1205`. Below is an example response based on the supplied mainnet configuration.
```json
{"jsonrpc":"2.0","id":1,"result":"0x1205"}
```
`eth_chainId` returns the chain ID as a hexadecimal string. The call follows the [Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_chainid). If the response differs, first check the RPC address and network settings. After a connection error or timeout, confirm a valid response before proceeding.
## Contract development and compatibility
Use EVM-compatible tools, but verify the EVM version, compiler and bytecode supported by the actual client. Compiler restrictions in older documents should not be treated as confirmed requirements of the current version.
Build contracts with settings compatible with the target network, and validate permissions, transfers and failure handling before deployment. Record tool versions, build settings and deployment results together.
## Gas and fees
Gas measures work; gas price is the cost per unit of work. Network fees are generally calculated as `gas used × gas price`. Actual costs depend on the execution path and state.
VeryChat’s free profile USDT transfers are an app service policy. The same terms do not apply to every smart-contract call or external-wallet transaction.
## Deployment and operations checks
Verify the deployed network, contract address and transaction receipt. Check permissions and both successful and failed behavior, and maintain publishable contract source and version records. Describe security audits only on the basis of confirmed firms, versions, scopes and reports.
The homepage introduces **VeryCloud as a cloud for web-service deployment**. Its role differs from VeryChain consensus and rewards; service addresses and actual availability are covered in separate guidance.
For node downloads, installation and synchronization, see [VeryChain and nodes — running and operating a node](/whitepaper/en/verychain/#node-operation).
## The role of public status data
Node status and advertising status are separate datasets. Remaining amounts, base rewards and proof rewards in the node API describe node conditions; usage, distribution and burn amounts in the advertising API describe campaign results. Preserve reference times and sources, and show the last valid data’s time if a request fails.
Node status uses public queries. Authenticated advertising-status requests are handled on the server, and only aggregate fields intended for publication reach the webpage. Authentication tokens must not appear in the browser or downloadable documents.
---
# 16. Terms, policies, and whitepaper history
Definitions for services, assets, and rewards, confirmed policies, open questions, disclaimers, references, and document history.
Updated: 2026-10-08
## Glossary
### Services and assets
| Term | Meaning in this whitepaper |
| --- | --- |
| VeryNetwork | The full ecosystem connecting people, services, and economic activity |
| VeryChain | The VERY blockchain network |
| VeryChat | The app at the center of conversation, channels, and participation |
| VeryWallet | In-app wallet, asset management, and transfers |
| VeryPOS | A platform for stablecoin payments and order, product, and sales management |
| VeryAds | The advertising platform using VERY for ad spend |
| VeryPay | The service name associated with registering and discovering shops accepting VERY |
| VERY | The asset used for ecosystem participation, use, and distribution |
| USDT | A stablecoin separate from VERY. Support must be checked per network. |
| Credits | Units used within a particular service; not automatically exchangeable 1:1 for VERY. |
### Distribution and rewards
| Term | Meaning |
| --- | --- |
| Total allocation | The amount designated by policy for a particular purpose |
| Amount paid | The amount actually paid under the relevant policy |
| Circulating supply | An amount reflecting the definition of circulation and locking; not identical to allocation |
| Fruit harvest | VeryChat's participation reward flow; not the same as block production |
| Halving | A rule that halves the base reward when a defined condition is reached |
| Invitation level | The criterion setting the fruit reward multiplier by invitation count |
| Friend boost | An extra factor based on the share of friends mining together at eligible levels |
| Buyback | Purchasing VERY again using available funds |
| Burn | Removing assets through a defined procedure; separate from purchasing |
| Node proof | Verifying eligibility and status in the node program; separate from consensus authority |
### Network
EVM is the smart-contract execution environment; RPC is the interface clients use to request network operations; Chain ID identifies a chain.
“Examples” illustrate calculations and structures. “Current tier” refers to the stated verification date, not a live balance or settlement.
## Policy verification record
### Basis of this edition
First written on **October 1, 2026**. **On October 7, 2026, 16 chapters were updated against all product and policy pages of the current website.** The update includes tokenomics changes, team vesting and payment rules, desktop, translation, advertising, shop management, and expanded reward tiers. Chapters explain products and rewards using the latest direction and policies confirmed by the project. Conflicting figures were not filled with estimates.
### Policies incorporated
| Item | Adopted basis |
| --- | --- |
| App participation rewards | Managed within the combined VeryChat allocation; no fixed sub-allocations for fruit, invitations, channels, or staking |
| Channel rewards | Subscription and staking rewards have not launched |
| Total allocation | 10 billion VERY: community and marketing 56%, team and advisors 19%, treasury and grants 5%, investors 10%, liquidity 10% — changed October 7, 2026 |
| Community and marketing | VeryChat rewards 3.4 billion, marketing 200 million, node validator rewards 2 billion VERY |
| Team vesting | 48 months from joining: 25% at the 12-month cliff, remaining 75% monthly and linearly over the following 36 months |
| Team lockup and payment | 12-month lockup after listing; installment payments begin after unlock under the prescribed schedule |
| Fruit rewards | Cumulative thresholds 300M / 500M / 700M / 1B / 1.4B / 1.8B / 2.2B; 12-hour base rewards 4.8 / 2.4 / 1.2 / 0.6 / 0.3 / 0.15 / 0.075 VERY |
| Invitation halving | The website's seven tiers: 500K / 2.5M / 6.5M / 7M / 15M / 31M / 63M+ registered users |
| Friend boost example | Formula corrected to `4.8 × 5 × (1 + 6/15) = 33.6 VERY` |
| Ad-spend distribution | Users and channels 50% / node proof participants 20% / burn 30% |
| Node NFTs | 8,000 total; contribution-based distribution after the initial sale of 1,600 |
| Node rewards | Initial allocation 2 billion VERY; valid proof participation adds 100% of the base reward |
| Service roles | Distinguishes USDT-centered payments from VERY's ecosystem use and distribution |
### Tokenomics change — October 7, 2026
Community and marketing changed from 5.1 to 5.6 billion VERY, and treasury and grants from 1 billion to 500 million. VeryChat rewards increased from the previous app reward total of 2.9 billion to 3.4 billion. Total supply remains 10 billion VERY. Previous tables and diagrams are preserved under [previous token allocation](/whitepaper/en/tokenomics/#allocation-history).
This change concerns overall allocation and total VeryChat rewards. Detailed distribution and payment conditions for individual rewards, and contract-specific vesting, remain governed by their own policies; they are not recalculated from the allocation change alone.
### Team vesting and payment rules — October 7, 2026
Project-provided policy establishes four-year vesting from joining, a one-year cliff, and monthly linear vesting afterward. A 12-month lockup follows listing; actual payments occur in installments after unlock according to the prescribed schedule. See [Vesting and payments](/whitepaper/en/vesting/) for the principles.
### Details requiring further confirmation
#### Later invitation reward tiers
[Invitation rewards](/whitepaper/en/invitations/) now use the current website's seven signup thresholds and rates. Different later thresholds from earlier documents are excluded. Total payouts cannot be calculated from signup thresholds alone without confirming eligible recipients and event usage.
Calculating final exhaustion requires confirmation of event usage, the unit of eligible recipients, and whether rewards for both parties are included.
#### Redistribution within the 50% ad share
The latest overall split is 50/20/30. The detailed division between users and channels and its connection to channel staking funds remain undecided. Previous separate formulas for main and channel advertising are not applied additionally.
#### Staking examples
Operator 20% / participant 80% is an internal channel distribution design. APY examples with unclear funding formulas and periods are not presented as current yields. Locking, unlocking, time weighting, and the latest funding structure require confirmation.
#### Reward measurement and operating settings
Unconfirmed details have not been invented: the scope and timing of channel reward denominators, whether inviters count in friend boosts, and exact node-proof payment cycles or disqualification handling. Actual popular-post algorithm weights are not treated as public.
#### Release status and technical versions
Channel subscription and staking rewards have not launched. MCP, VERY purchase and top-up in the advertiser interface, expanded cash and local payment integrations, and AI summaries are marked as planned or future expansion. VERY Mainnet RPC (`https://rpc.verylabs.io`), Chain ID `4613` (HEX `0x1205`), and currency `VERY` reflect current connection details supplied by the project. See [public network information](/whitepaper/en/verychain/#공개-네트워크-정보) for full settings. Node environments, file structure, and commands follow official 2026 packages. Downloads and installation and operating steps are in [VeryChain and nodes](/whitepaper/en/verychain/#node-operation).
### Metrics and sources
| Metric | Measurement basis |
| --- | --- |
| Map user scale | Estimated location totals from connection logs; different from account database signups |
| 147 countries and regions | Countries and regions of users completing KYC rounds 1 and 2 |
| KYC and node withdrawals | Amounts supplied by the operations team on October 5, 2026; marketing excluded |
| POREMI campaign results | September 1–15, 2026, excluding South Korea; measured by VeryAds and POREMI |
| Node and advertising status | Separate metrics tied to each API's retrieval or snapshot time |
Presentation figures describe their publication time; website data describes each collection date. “Current reward tier” uses the position supplied by the project as of September 27, 2026, not a live API value.
This record preserves detail while preventing figures from different periods from appearing to be one policy. Confirmed changes update both the relevant chapter and this record.
## Disclaimer
### For information
This whitepaper explains the VERY ecosystem's services and technical and economic structure. It is not financial, legal, or tax advice, a recommendation to buy or sell an asset, an investment contract, or a promise of returns. Users should conduct their own review and seek independent professional advice when needed.
### Price and usage risks
Digital asset values can fluctuate and losses can occur. Participation rewards, burning, user growth, and past campaign performance do not guarantee a higher VERY price or future returns. Technical and operating risks include lost wallet information, incorrect transfers, network failures, and service interruptions.
### Plans, figures, and changes
Planned features and roadmaps describe development direction at the time of writing; scope and timing may change with market, technical, and operating conditions. Statistics apply to their stated measurement basis and time; demos and calculations do not represent actual payments or results. Check official service notices and applicable terms for changing policies and usage conditions.
### Scope and rights
Outcomes of decisions based solely on this whitepaper are not guaranteed. Specific service use and responsibilities follow applicable law and the service's terms. Trademarks and works mentioned belong to their respective rights holders. External content and services follow their operators' conditions.
## Sources and document history
### Document information
- Version: **2026.10 English edition; based on the Korean review edition**
- First written: **October 1, 2026**
- Full update: **October 7, 2026**, checked against product and policy pages for the website's four services
- Policy change: **October 7, 2026 tokenomics update** — [allocation history](/whitepaper/en/tokenomics/#배분-변경-기록)
- Team policy: **October 7, 2026 vesting, lockup, and payment rules** — [Vesting and payments](/whitepaper/en/vesting/)
- Scope: vision, products, tokenomics, participation rewards, channel algorithms, and node policy
- Structure: **14 main chapters and 3 appendix chapters**, grouping product explanations and reward and payment policies, with formulas and operating procedures in subsections
[Download the full whitepaper as Markdown](/whitepaper/en/whitepaper.md)
### References for the problem and vision
[GWDC 2026 VERY LABS presentation coverage — TokenPost](https://www.tokenpost.kr/news/insights/416214), September 30, 2026. Referenced for the emphasis on actual user experience over technology alone. Article text and photos are linked, not republished.
### Documents by topic
| Topic | Chapters in this whitepaper |
| --- | --- |
| Getting started | [Introduction and vision](/whitepaper/en/) · [Ecosystem overview](/whitepaper/en/ecosystem/) |
| Everyday services | [VeryChat — conversation, translation, wallet, transfers](/whitepaper/en/verychat/) · [VeryPOS](/whitepaper/en/verypos/) · [VeryAds — advertising and MCP](/whitepaper/en/veryads/) |
| VERY economy | [Tokenomics](/whitepaper/en/tokenomics/) · [Vesting and payments](/whitepaper/en/vesting/) · [VERY circulation and ad distribution](/whitepaper/en/economy/) |
| Participation and rewards | [Fruit rewards](/whitepaper/en/mining/) · [Invitation rewards and friend boost](/whitepaper/en/invitations/) · [Channels and community rewards](/whitepaper/en/channels/) |
| Network and trust | [VeryChain and nodes](/whitepaper/en/verychain/) · [Community and plans](/whitepaper/en/community/) · [Identity and privacy](/whitepaper/en/safety/) |
| Appendix | [Developer guide](/whitepaper/en/developers/) · [Terms, policies, and history](/whitepaper/en/references/) · [Linktree](/whitepaper/en/linktree/) |
### Included in this website reconciliation
- VeryChat: free profile-based USDT transfers, on-device translation demo, five Mac and Windows screens, and credit distinctions
- VeryPOS: customer QR orders, USDT and optional VERY payments, merchant order, product, and sales management, and separate merchant applications
- VeryAds: six placements, creative, budget, and reporting screens, the POREMI campaign, and planned MCP
- Rewards: seven fruit tiers halving every 400 million after 1 billion cumulative distribution, and invitation tiers based on registered users
- Ecosystem: KYC and node withdrawals, advertising metrics, and the basis of user-distribution estimates
### Document updates
Changes in policy or product availability update both the relevant chapter and the [policy verification record](/whitepaper/en/references/#policy-record). Each chapter distinguishes confirmed figures, planned features, and operating conditions needing further confirmation.
Sources for this chapter:
- https://www.tokenpost.kr/news/insights/416214
---
# 17. Official services and channels
Find the VERY ecosystem’s official services, news channels and key guides in one place.
Updated: 2026-10-08
## Linktree — official services and channels
| Category | Official link | Purpose |
| --- | --- | --- |
| VeryNetwork | verylabs.io | Ecosystem and network overview |
| VeryChat | verychat.io | Messenger, wallet and app downloads |
| VeryAds | veryads.io | Ad placements and campaign guidance |
| VeryPOS | verypos.io | Payments and store operations |
| VeryPay | pay.verychat.io | Merchant map and merchant applications |
| VeryScan | veryscan.io | Blocks and transactions |
| Medium | Official VERY LABS Medium | Project news and articles |
| X | @verylabs | Official news and announcements |
Choose a node client for your environment from VeryChain and nodes: downloads. You can also view the roadmap, team and disclaimer.
Choose items
Choose payment method
Payment complete
Order management
Product management
Sales history
