# Introduction

Welcome to StakeStone!

StakeStone envisions and is committed to building the next gen **crypto-native neo bank:** a blockchain-based financial infrastructure that replaces centralized intermediation with programmable, trustless systems.

&#x20;•  Settlement Layer: High-performance blockchain networks provide native clearing and settlement.

&#x20;•  Identity Layer: Intuitive identity solutions enable fully self-custodied on-chain accounts.

&#x20;•  Interaction Layer: Account Abstraction supports native on-chain smart operations.

&#x20;•  Intelligence Layer: With the AP2 (Agent Payments Protocol), the system is AI- and machine-payment-compatible.

Our architecture is designed to empower both human and machine agents to transact globally with real-time, low-cost, and secure settlements, forming the cornerstone that we believe as the future of an autonomous, borderless financial era.

For more details, follow us on X, TG, and Medium!

Twitter: [https://twitter.com/Stake\_Stone](https://twitter.com/Stake_Stone?s=20)

Telegram: <https://t.me/+afYqz2KG_YNlNzNl>

Medium: <https://medium.com/@Stake_Stone_>


# What is Stone Wallet?

Stone Wallet is a next-generation crypto wallet built by StakeStone. Designed to feel like a global, digital bank account, but powered entirely by blockchain.&#x20;

Current solutions for crypto payments face many challenges, including but not limited to:&#x20;

1. Bad user experience: transaction failure, lagging, etc.
2. High gas fees: not suitable for small value transactions

Stone Wallet addresses the market's need for a global, smart money account that not only accumulates yields but also facilitates real-time small value payments with low gas fees and instant settlement. At its core, Stone Wallet lets you store, send, pay, receive, and grow your money in one place, without the friction of traditional banking or the complexity of DeFi.&#x20;


# Frequently Asked Questions

Everything you need to get started.


# How to Create Your Account

Getting started with Stone Wallet is fast, easy, and crypto-optional. You can sign up in seconds using one of your existing social accounts.

{% stepper %}
{% step %}

### **Choose login method**

You can sign up using:

* Google
* X (Twitter)
* Telegram
* Email

No password or private keys to remember, just link your socials.
{% endstep %}

{% step %}

### **Verify and Create Your Account**

Once you choose a login method:

* We'll verify your identity with your selected platform
* If it's your first time, we'll auto-create your Stone Wallet smart account.
  {% endstep %}

{% step %}

### **Start Receiving Payments**

After logging in, you can start receiving and sending payments right away! You will get a unique Stone Wallet payment link and QR code to share with payees.
{% endstep %}
{% endstepper %}


# How to Deposit Funds into Your Account

Depositing funds into your Stone account is simple and flexible. The following guide will cover two methods of depositing funds: **fiat** (e.g., cards, banks, etc.) or **crypto** from an external wallet.

***

## Depositing from Fiat Sources <a href="#h_72a907571d" id="h_72a907571d"></a>

You can deposit local currency into Stone Wallet and receive stablecoins (e.g., USDT, USDC, or USD1) in your balance.

### How it works: <a href="#h_80552ba544" id="h_80552ba544"></a>

1. On your dashboard, tap **Deposit** → **Card & Debit Card**
2. Enter the amount and select the stablecoin you want to receive (e.g. USDT)
3. Choose the currency you’ll pay in (e.g. USD, EUR, IDR, etc.)
4. Select a payment method:
   * Credit/Debit Card
   * Apple Pay/Google Pay
   * PayPal
   * Local Bank Transfer
   * etc.&#x20;
5. View real-time offers from providers like AlchemyPay, Banxa, Transak, etc.
6. Choose the best rate and complete the deposit with your selected provider

Stone Wallet automatically shows the best rate and fastest settlement provider for your region.

***

## Depositing Crypto from a Wallet <a href="#h_c3d297283c" id="h_c3d297283c"></a>

Already have crypto in another wallet? You can directly deposit stablecoins into your Stone account.

### How it works: <a href="#h_52088f172b" id="h_52088f172b"></a>

1. On the dashboard, tap **Deposit → Crypto Wallet**
2. Choose the asset you want to deposit:
   * USDT
   * USDC
   * USD1
3. Select the correct network:
   * Ethereum (ERC-20)
   * BNB Smart Chain (BEP-20)
4. You’ll be shown a wallet address and QR code linked to your Stone account
5. Send the stablecoins from your wallet to the address shown

⚠️  Make sure to double-check the network and token type before sending.

⚠️  Sending unsupported tokens or using the wrong network could result in lost funds.

After the transaction confirms, your Stone balance will update automatically.&#x20;


# How to Send Payments

Stone Wallet allows you to make payments both in everyday real-world settings and directly to other users.

Users can pay merchants using QR codes in supported countries, or send funds to individuals using links or personal QR codes.

***

### Pay at Stores with QR Code (Retail Payments)

Stone Wallet supports QR-based payments at merchants in supported regions, allowing users to pay directly at checkout using local QR payment systems, without needing cash or traditional bank apps.

**To pay in-store:**

1. Open the app and tap **Scan**
2. Scan the merchant’s QR code
3. Enter the payment amount
4. Review the details and complete the payment

Once confirmed, the payment is processed and completed at the point of sale.

***

### Supported Payment Networks

Stone Wallet supports QR-based payments across multiple countries through local payment networks.

Availability may vary depending on region, merchant type, and integration status.

#### Currently Supported&#x20;

Stone Wallet QR payments are currently available in:

| Country     | Supported QR Codes | Unsupported QR Codes                        |
| ----------- | ------------------ | ------------------------------------------- |
| Singapore   | PayNow             | NETS, SGQR (non-PayNow), GrabPay, ShopeePay |
| Thailand    | PromptPay          | TrueMoney, LINE Pay, ShopeePay              |
| Vietnam     | VietQR             | MoMo, ZaloPay, bank QR codes                |
| Philippines | QRPh               | GCash (private QR), Maya, GrabPay           |
| Cambodia    | KHQR               | Wing, TrueMoney, bank QR codes              |
| Laos        | BCEL OnePay        | Bank QR codes, wallet QR codes              |
| Mongolia    | QPay               | Bank QR codes, wallet QR codes              |

In addition, Stone Wallet has integration capability with:

* WeChat Pay
* Alipay HK
* Korea ZeroPay

These integrations may be selectively enabled depending on use case and compliance requirements.

#### Coming Soon&#x20;

Stone Wallet is continuously expanding support for additional countries and local QR payment networks.

The following integrations are currently in progress:

**Targeted for March:**&#x20;

* Peru
* Bolivia
* Colombia
* Argentina
* Brazil

**Targeted for April:** Indonesia (QRIS)

**Targeted for May:** Malaysia (DuitNow)

**Targeted for June**:&#x20;

* South Korea (ZeroPay)
* Japan (PayPay)
* Taiwan (TWQR)

Timelines are indicative and subject to change based on integration and regulatory requirements.

Coverage will continue to expand as new integrations are completed.

***

### Pay Individuals (P2P)

You can also make payments directly to other users located anywhere in the world.

**To send a payment:**

1. Open the app and go to **Transfer**&#x20;
2. Paste the recipient’s wallet address, or the email/username tied to their stone wallet account, or scan their QR code
3. Enter or confirm the amount
4. Review and confirm the payment

Funds are transferred directly to the recipient’s wallet.


# How to Receive Payments

Stone Wallet allows you to receive payments globally in a simple and flexible way, whether you’re getting paid by individuals, clients, or businesses. There are no platform fees on incoming payments, and funds are received directly into your wallet balance.

### Receiving Payments: Available Methods <a href="#h_a89249a085" id="h_a89249a085"></a>

#### 1. Your Unique Payment Link <a href="#h_7ba50a4b89" id="h_7ba50a4b89"></a>

**Each Stone Wallet account comes with a unique payment link.** This link can be shared anywhere, including messaging apps, email, or social platforms. The sender can complete the payment directly through the link, without requiring additional setup.

This method is suitable for:

* Remote work and freelance payments
* Cross-border transfers
* Peer-to-peer payments

#### 2. QR Code for In-Person or Offline Payments <a href="#h_d6cf6ae171" id="h_d6cf6ae171"></a>

Stone Wallet provides a personal QR code that others can scan to send you funds instantly.

This is useful for:&#x20;

* Meetups, events, or merch tables
* In-person payments
* Offline or cashless environments

### Receiving  <a href="#h_0a1fa080ac" id="h_0a1fa080ac"></a>

Payments received through Stone Wallet are:

* Instant or near-instant depending on the method
* Settled directly into your wallet balance
* Available for immediate use or further transactions

Your balance remains fully accessible after receiving funds, and can be used at any time for transfers or payments without lockup periods.&#x20;


# How to Set or Clear a Payment Amount

Stone Wallet allows you to request a fixed payment amount when sharing your QR code or payment link. This is useful when you want the sender to pay a specific value instead of entering it manually.

***

### Setting an Amount

1. From the Pay screen, tap Set Amount.

   Enter the amount you would like to receive, then confirm.
2. Once set, the amount will appear at the top of your Pay screen, and your QR code will automatically include this value for the recipient.&#x20;

Anyone scanning your QR code or opening your payment link will see the preset amount and can proceed directly with payment.

#### Clearing an Amount

If you have previously set an amount, you can remove it at any time.

**From the Pay screen, tap Clear Amount.**

Your QR code will return to an open-ended state, allowing the sender to input their own amount.

***

You can update or clear the amount at any time before a payment is made.

This feature works for both QR code payments and payment links.


# How to Withdraw Your Funds

Stone Wallet allows you to withdraw your funds at any time, either to a bank account or payment method, or to an external crypto wallet. You can choose the option that best fits your needs depending on how you want to use your funds.

***

### Withdraw to Fiat

You can convert your balance into local currency and receive it through supported payment methods.

Available payout methods may include:

* Visa/Mastercard
* Digital payment methods such as Apple Pay and Google Pay
* Local bank transfers depending on your region

#### How it works

1. From the app, go to **Withdraw** and select your preferred payout method.
2. Choose the asset you want to withdraw and enter the amount.
3. Select the currency you want to receive, then review the available payout options. You will be shown the final amount, fees, and estimated processing time before confirming.
4. Once confirmed, your withdrawal will be processed and sent to your selected method.

#### Processing time

Processing times vary depending on the payout method and provider.

Some withdrawals may complete within minutes, while others may take longer depending on banking systems and regional support.

***

### Withdraw to Crypto Wallet

You can also transfer your funds directly to an external crypto wallet.

This is useful if you want to:

* Self-custody your assets
* Use funds on other platforms
* Transfer to centralized exchanges or other services

#### How it works

1. From the app, go to **Withdraw → Crypto Wallet**.
2. Select the asset and network you want to use.
3. Enter the withdrawal amount and paste your wallet address.
4. Review the transaction details, including network fees and final amount.
5. Confirm the transaction to proceed.

***

### Important Notes

Always ensure that the wallet address and network match before confirming a crypto withdrawal.

Sending funds to an unsupported address or incorrect network may result in permanent loss.

Withdrawal availability, limits, and supported methods may vary depending on your region and compliance requirements.


# Which Stablecoins and Chains does Stone Wallet Support?

| Token           | Chain(s) available                                   | Description                                                               |
| --------------- | ---------------------------------------------------- | ------------------------------------------------------------------------- |
| USDT (Tether)   | <p>Ethereum (ERC-20)<br>BNB Smart Chain (BEP-20)</p> | Most widely used stablecoin, issued by Tether and pegged to US dollar.    |
| USDC (USD Coin) | <p>Ethereum (ERC-20)<br>BNB Smart Chain (BEP-20)</p> | Fully-backed and regulated USD-pegged stablecoin                          |
| USD1            | <p>Ethereum (ERC-20)<br>BNB Smart Chain (BEP-20)</p> | A new institutional-grade stablecoin backed by short-term U.S. Treasuries |


# Managing Notifications

#### To turn notifications on or off: <a href="#h_ec290b9ec1" id="h_ec290b9ec1"></a>

1. Go to Settings
2. Under your profile, toggle the Notification switch

This setting controls in-app alerts like tips received, withdrawals, or updates. Email notification preferences are managed separately.


# Language & Currency Preferences

Make Stone Wallet work for you wherever you are by setting your preferred language and currency display.

**To change your display settings:**

1. Tap your avatar → go to **Settings**
2. Scroll to the **General** section
3. Tap **Currency** to change your default display unit (e.g. USD, EUR, IDR)
4. Tap **Language** to switch to another language (currently: English only)

<br>


# Is Stone Wallet Secure?

Stone Wallet is designed to be secure, private, and fully user-controlled, combining self-custody with a simplified user experience. Your funds always remain under your control, and the system is built to minimize risk while keeping the experience simple.

***

### Non-Custodial by Design

Stone Wallet uses a non-custodial smart wallet architecture.

This means:

* You are the only one who can authorize transactions
* No one  can move your funds without your approval
* Your assets are not held or controlled by a centralized party. Instead, they are secured on-chain and managed through your wallet.

***

### Secure Key Management

Stone Wallet uses secure key management powered by MPC (Multi-Party Computation). This removes the need for traditional seed phrases while avoiding a single point of failure.

Your wallet access is protected through distributed key security, making it both safer and easier to use compared to traditional crypto wallets.

***

### Trusted Payment Infrastructure

Deposits and withdrawals are supported through regulated third-party providers.

These providers operate under applicable compliance standards, including KYC and AML requirements where necessary. This ensures that fiat on- and off-ramps are handled securely and reliably.


# How Stone Wallet Handles Your Data

Your privacy matters. Stone Wallet collects only the data needed to provide secure payments and personalized experiences.

### What we collect: <a href="#h_892f862fa1" id="h_892f862fa1"></a>

* Your IP address (for fraud prevention and regional settings)
* Info you enter (email, wallet address, username, avatar, etc.)

We do not sell your data or track you unnecessarily.

We use secure cloud providers like Firebase and AWS to protect it.


# What if I Lose Access to My Account?

If you’re unable to access your Stone Wallet account, don’t worry. There are a few ways to regain access.

***

### Try logging in again

Start by logging out, refreshing the page and logging in using the method you originally used to create the account. Stone Wallet supports multiple login methods (such as Google or email), and in some cases, these may be linked to the same account.

If you previously signed up with Google, you may still be able to access your account using your email login, depending on how your account was set up.

### Still can’t access your account?

If you’re unable to log in, please contact support (<official@stakestone.io>) and include:

* the login method(s) you may have used
* the email address associated with your account

Our team will help you verify your identity and restore access.

***

### Notes

For the best experience, we recommend continuing to use the same login method you used during sign-up.

If you’re unsure which method was used, support can help you identify and recover your account.


# Is there a minimum amount for deposits and withdrawals?

Yes.

To keep transactions efficient and cost-effective, Stone Wallet has a minimum of $10 USD (or equivalent) for both:

* Deposits
* Withdrawals

You won’t be able to process amounts below this limit. If you try to send less than $10, you’ll see an error message prompting you to enter a higher amount.

This minimum helps us reduce network fees and maintain fast, low-cost service for everyone.


# Does Stone Wallet take commissions or platform fees?

Stone Wallet does not charge platform fees or take commissions on your funds.

What you receive is what you keep.

***

#### Fees Explained

Currently, network gas fees are subsidized, so you will not be charged gas for transactions.

The only costs that may apply are:

* network-related costs (where applicable in the future)
* currency conversion rates when exchanging between assets or fiat
* third party provider fees

There are no additional platform fees or hidden charges applied by Stone Wallet.


# Supported countries & currencies for Deposits & Withdrawals

Stone Wallet supports users globally across 200+ countries and territories, with payments available in 100+ local and digital currencies.

Whether you’re receiving funds in fiat or digital assets, Stone Wallet makes it seamless to hold, convert, and use your balance no matter where you’re based.

#### Supported Countries & Currencies (A–Z)

* Afghanistan – Afghan Afghani (AFN, ؋)
* Albania – Albanian Lek (ALL, L)
* Algeria – Algerian Dinar (DZD, د.ج)
* American Samoa – US Dollar (USD, $)
* Andorra – Euro (EUR, €)
* Angola – Angolan Kwanza (AOA, Kz)
* Anguilla – Eastern Caribbean Dollar (XCD, $)
* Antigua and Barbuda – Eastern Caribbean Dollar (XCD, $)
* Argentina – Argentine Peso (ARS, $)
* Armenia – Armenian Dram (AMD, ֏)
* Aruba – Aruban Florin (AWG, ƒ)
* Australia – Australian Dollar (AUD, A$)
* Austria – Euro (EUR, €)
* Azerbaijan – Azerbaijani Manat (AZN, ₼)
* Bahamas – Bahamian Dollar (BSD, B$)
* Bahrain – Bahraini Dinar (BHD, .د.ب)
* Bangladesh – Bangladeshi Taka (BDT, ৳)
* Barbados – Barbadian Dollar (BBD, Bds$)
* Belarus – Belarusian Ruble (BYN, Br)
* Belgium – Euro (EUR, €)
* Belize – Belize Dollar (BZD, BZ$)
* Benin – West African CFA Franc (XOF, CFA)
* Bermuda – Bermudian Dollar (BMD, BD$)
* Bhutan – Bhutanese Ngultrum (BTN, Nu.)
* Bolivia – Bolivian Boliviano (BOB, Bs.)
* Bonaire, Saint Eustatius and Saba – US Dollar (USD, $)
* Bosnia and Herzegovina – Convertible Mark (BAM, KM)
* Botswana – Botswana Pula (BWP, P)
* Bouvet Island – Norwegian Krone (NOK, kr)
* Brazil – Brazilian Real (BRL, R$)
* British Indian Ocean Territory – US Dollar (USD, $)
* British Virgin Islands – US Dollar (USD, $)
* Brunei – Brunei Dollar (BND, B$)
* Bulgaria – Bulgarian Lev (BGN, лв)
* Burkina Faso – West African CFA Franc (XOF, CFA)
* Burundi – Burundian Franc (BIF, FBu)
* Cambodia – Cambodian Riel (KHR, ៛)
* Cameroon – Central African CFA Franc (XAF, FCFA)
* Canada – Canadian Dollar (CAD, C$)
* Cape Verde – Cape Verdean Escudo (CVE, $ or Esc)
* Cayman Islands – Cayman Islands Dollar (KYD, CI$)
* Central African Republic – Central African CFA Franc (XAF, FCFA)
* Chad – Central African CFA Franc (XAF, FCFA)
* Chile – Chilean Peso (CLP, $)
* Christmas Island – Australian Dollar (AUD, A$)
* Cocos (Keeling) Islands – Australian Dollar (AUD, A$)
* Colombia – Colombian Peso (COP, $)
* Comoros – Comorian Franc (KMF, CF)
* Cook Islands – New Zealand Dollar (NZD, NZ$)
* Costa Rica – Costa Rican Colón (CRC, ₡)
* Croatia – Euro (EUR, €)
* Cuba – Cuban Peso (CUP, $)
* Curaçao – Netherlands Antillean Guilder (ANG, ƒ)
* Cyprus – Euro (EUR, €)
* Czechia – Czech Koruna (CZK, Kč)
* Democratic Republic of the Congo – Congolese Franc (CDF, FC)
* Denmark – Danish Krone (DKK, kr)
* Djibouti – Djiboutian Franc (DJF, Fdj)
* Dominica – Eastern Caribbean Dollar (XCD, $)
* Dominican Republic – Dominican Peso (DOP, RD$)
* East Timor – US Dollar (USD, $)
* Ecuador – US Dollar (USD, $)
* Egypt – Egyptian Pound (EGP, £ or ج.م)
* El Salvador – US Dollar (USD, $)
* Equatorial Guinea – Central African CFA Franc (XAF, FCFA)
* Eritrea – Eritrean Nakfa (ERN, Nfk)
* Estonia – Euro (EUR, €)
* Eswatini – Swazi Lilangeni (SZL, L or E)
* Ethiopia – Ethiopian Birr (ETB, Br)
* Falkland Islands – Falkland Islands Pound (FKP, £)
* Faroe Islands – Danish Krone (DKK, kr)
* Federated States of Micronesia – US Dollar (USD, $)
* Fiji – Fijian Dollar (FJD, FJ$)
* Finland – Euro (EUR, €)
* France – Euro (EUR, €)
* French Guiana – Euro (EUR, €)
* French Polynesia – CFP Franc (XPF, ₣)
* French Southern and Antarctic Lands – Euro (EUR, €)
* Gabon – Central African CFA Franc (XAF, FCFA)
* Gambia – Gambian Dalasi (GMD, D)
* Georgia – Georgian Lari (GEL, ₾)
* Germany – Euro (EUR, €)
* Ghana – Ghanaian Cedi (GHS, ₵)
* Gibraltar – Gibraltar Pound (GIP, £)
* Greece – Euro (EUR, €)
* Greenland – Danish Krone (DKK, kr)
* Grenada – Eastern Caribbean Dollar (XCD, $)
* Guadeloupe – Euro (EUR, €)
* Guam – US Dollar (USD, $)
* Guatemala – Guatemalan Quetzal (GTQ, Q)
* Guernsey – Guernsey Pound (GGP, £)
* Guinea – Guinean Franc (GNF, FG)
* Guinea-Bissau – West African CFA Franc (XOF, CFA)
* Guyana – Guyanese Dollar (GYD, G$)
* Haiti – Haitian Gourde (HTG, G)
* Heard Island and McDonald Islands – Australian Dollar (AUD, A$)
* Honduras – Honduran Lempira (HNL, L)
* Hong Kong – Hong Kong Dollar (HKD, HK$)
* Hungary – Hungarian Forint (HUF, Ft)
* Iceland – Icelandic Króna (ISK, kr)
* India – Indian Rupee (INR, ₹)
* Indonesia – Indonesian Rupiah (IDR, Rp)
* Iran – Iranian Rial (IRR, ﷼)
* Iraq – Iraqi Dinar (IQD, ع.د)
* Ireland – Euro (EUR, €)
* Isle of Man – Manx Pound (IMP, £)
* Israel – Israeli New Shekel (ILS, ₪)
* Italy – Euro (EUR, €)
* Ivory Coast – West African CFA Franc (XOF, CFA)
* Jamaica – Jamaican Dollar (JMD, J$)
* Japan – Japanese Yen (JPY, ¥)
* Jersey – Jersey Pound (JEP, £)
* Jordan – Jordanian Dinar (JOD, د.ا)
* Kazakhstan – Kazakhstani Tenge (KZT, ₸)
* Kenya – Kenyan Shilling (KES, KSh)
* Kiribati – Kiribati Dollar (KID, $)
* Kosovo – Euro (EUR, €)
* Kuwait – Kuwaiti Dinar (KWD, د.ك)
* Kyrgyzstan – Kyrgyzstani Som (KGS, с)
* Laos – Lao Kip (LAK, ₭)
* Latvia – Euro (EUR, €)
* Lebanon – Lebanese Pound (LBP, ل.ل)
* Lesotho – Lesotho Loti (LSL, L)
* Liberia – Liberian Dollar (LRD, L$)
* Libya – Libyan Dinar (LYD, ل.د)
* Liechtenstein – Swiss Franc (CHF, CHF)
* Lithuania – Euro (EUR, €)
* Luxembourg – Euro (EUR, €)
* Macao – Macanese Pataca (MOP, MOP$)
* Madagascar – Malagasy Ariary (MGA, Ar)
* Malawi – Malawian Kwacha (MWK, MK)
* Malaysia – Malaysian Ringgit (MYR, RM)
* Maldives – Maldivian Rufiyaa (MVR, .ރ)
* Mali – West African CFA Franc (XOF, CFA)
* Malta – Euro (EUR, €)
* Marshall Islands – US Dollar (USD, $)
* Martinique – Euro (EUR, €)
* Mauritania – Mauritanian Ouguiya (MRU, UM)
* Mauritius – Mauritian Rupee (MUR, ₨)
* Mayotte – Euro (EUR, €)
* Mexico – Mexican Peso (MXN, $)
* Moldova – Moldovan Leu (MDL, L)
* Monaco – Euro (EUR, €)
* Mongolia – Mongolian Tögrög (MNT, ₮)
* Montenegro – Euro (EUR, €)
* Montserrat – Eastern Caribbean Dollar (XCD, $)
* Morocco – Moroccan Dirham (MAD, د.م.)
* Mozambique – Mozambican Metical (MZN, MT)
* Myanmar – Burmese Kyat (MMK, K)
* Namibia – Namibian Dollar (NAD, N$)
* Nauru – Australian Dollar (AUD, A$)
* Nepal – Nepalese Rupee (NPR, ₨)
* Netherlands – Euro (EUR, €)
* New Caledonia – CFP Franc (XPF, ₣)
* New Zealand – New Zealand Dollar (NZD, NZ$)
* Nicaragua – Nicaraguan Córdoba (NIO, C$)
* Niger – West African CFA Franc (XOF, CFA)
* Nigeria – Nigerian Naira (NGN, ₦)
* Niue – New Zealand Dollar (NZD, NZ$)
* Norfolk Island – Australian Dollar (AUD, A$)
* North Korea – North Korean Won (KPW, ₩)
* North Macedonia – Macedonian Denar (MKD, ден)
* Northern Mariana Islands – US Dollar (USD, $)
* Norway – Norwegian Krone (NOK, kr)
* Oman – Omani Rial (OMR, ر.ع.)
* Pakistan – Pakistani Rupee (PKR, ₨)
* Palau – US Dollar (USD, $)
* Palestine – Israeli New Shekel (ILS, ₪)
* Panama – Panamanian Balboa (PAB, B/.)
* Papua New Guinea – Papua New Guinean Kina (PGK, K)
* Paraguay – Paraguayan Guaraní (PYG, ₲)
* Peru – Peruvian Sol (PEN, S/.)
* Philippines – Philippine Peso (PHP, ₱)
* Pitcairn Islands – New Zealand Dollar (NZD, NZ$)
* Poland – Polish Złoty (PLN, zł)
* Portugal – Euro (EUR, €)
* Puerto Rico – US Dollar (USD, $)
* Qatar – Qatari Riyal (QAR, ر.ق)
* Republic of the Congo – Central African CFA Franc (XAF, FCFA)
* Romania – Romanian Leu (RON, lei)
* Russia – Russian Ruble (RUB, ₽)
* Rwanda – Rwandan Franc (RWF, FRw)
* Réunion – Euro (EUR, €)
* Saint Barthélemy – Euro (EUR, €)
* Saint Helena, Ascension and Tristan da Cunha – Saint Helena Pound (SHP, £)
* Saint Kitts and Nevis – Eastern Caribbean Dollar (XCD, $)
* Saint Lucia – Eastern Caribbean Dollar (XCD, $)
* Saint Martin – Euro (EUR, €)
* Saint Pierre and Miquelon – Euro (EUR, €)
* Saint Vincent and the Grenadines – Eastern Caribbean Dollar (XCD, $)
* Samoa – Samoan Tālā (WST, T)
* San Marino – Euro (EUR, €)
* Sao Tome and Principe – São Tomé and Príncipe Dobra (STN, Db)
* Saudi Arabia – Saudi Riyal (SAR, ر.س)
* Senegal – West African CFA Franc (XOF, CFA)
* Serbia – Serbian Dinar (RSD, дин.)
* Seychelles – Seychellois Rupee (SCR, ₨)
* Sierra Leone – Sierra Leonean Leone (SLL, Le)
* Singapore – Singapore Dollar (SGD, S$)
* Sint Maarten – Netherlands Antillean Guilder (ANG, ƒ)
* Slovakia – Euro (EUR, €)
* Slovenia – Euro (EUR, €)
* Solomon Islands – Solomon Islands Dollar (SBD, SI$)
* Somalia – Somali Shilling (SOS, Sh)
* South Africa – South African Rand (ZAR, R)
* South Georgia and South Sandwich Islands – Falkland Islands Pound (FKP, £)
* South Korea – South Korean Won (KRW, ₩)
* South Sudan – South Sudanese Pound (SSP, £)
* Spain – Euro (EUR, €)
* Sri Lanka – Sri Lankan Rupee (LKR, Rs)
* Sudan – Sudanese Pound (SDG, ج.س.)
* Suriname – Surinamese Dollar (SRD, $)
* Svalbard and Jan Mayen – Norwegian Krone (NOK, kr)
* Sweden – Swedish Krona (SEK, kr)
* Switzerland – Swiss Franc (CHF, CHF)
* Syria – Syrian Pound (SYP, £ or ل.س)
* Taiwan – New Taiwan Dollar (TWD, NT$)
* Tajikistan – Tajikistani Somoni (TJS, SM)
* Tanzania – Tanzanian Shilling (TZS, TSh)
* Thailand – Thai Baht (THB, ฿)
* Togo – West African CFA Franc (XOF, CFA)
* Tokelau – New Zealand Dollar (NZD, NZ$)
* Tonga – Tongan Paʻanga (TOP, T$)
* Trinidad and Tobago – Trinidad and Tobago Dollar (TTD, TT$)
* Tunisia – Tunisian Dinar (TND, د.ت)
* Turkey – Turkish Lira (TRY, ₺)
* Turkmenistan – Turkmenistan Manat (TMT, T)
* Turks and Caicos Islands – US Dollar (USD, $)
* Tuvalu – Tuvaluan Dollar (TVD, $)
* U.S. Virgin Islands – US Dollar (USD, $)
* Uganda – Ugandan Shilling (UGX, USh)
* Ukraine – Ukrainian Hryvnia (UAH, ₴)
* United Arab Emirates – UAE Dirham (AED, د.إ)
* United Kingdom – British Pound Sterling (GBP, £)
* United States – US Dollar (USD, $)
* United States Minor Outlying Islands – US Dollar (USD, $)
* Uruguay – Uruguayan Peso (UYU, $)
* Uzbekistan – Uzbekistani Som (UZS, so’m)
* Vanuatu – Vanuatu Vatu (VUV, VT)
* Vatican City – Euro (EUR, €)
* Venezuela – Venezuelan Bolívar (VES, Bs.D)
* Vietnam – Vietnamese Đồng (VND, ₫)
* Wallis and Futuna – CFP Franc (XPF, ₣)
* Western Sahara – Moroccan Dirham (MAD, د.م.)
* Yemen – Yemeni Rial (YER, ﷼)
* Zambia – Zambian Kwacha (ZMW, ZK)
* Zimbabwe – Zimbabwean Dollar (ZWL, Z$)
* Åland Islands – Euro (EUR, €)


# What if my payment isn’t going through?

If your payment fails or does not complete, it is usually due to temporary issues or incorrect details.&#x20;

### Paying a Merchant (QR Code)

**If you are paying in-store or scanning a merchant QR code:**

* Check that the QR code is supported by Stone Wallet and was scanned correctly and that the merchant details shown in the app are accurate.

If the payment does not go through, it may be due to:

* temporary network or processing delays
* unsupported QR format or payment network
* provider-side issues during routing

If a payment appears stuck or pending, do not resend the payment.

If the payment still fails after retrying, please contact <official@stakestone.io> and provide:&#x20;

* username/email registered in Stone wallet
* merchant name&#x20;
* screenshot of the payment screen if available&#x20;

***

### Paying an Individual (P2P)

If you are sending a payment to another user, make sure the payment link or QR code belongs to the correct recipient.

If you are entering details manually, double-check that all information is correct before confirming.

If sending to an external wallet, ensure:

* the wallet address is correct
* the selected network matches the recipient’s wallet

Most payments are completed within minutes. If the transaction is delayed, it may be due to network conditions or temporary processing issues.

If the payment does not go through or fails repeatedly, please contact support (<official@stakestone.io>) and include:

* recipient details (link, QR, or wallet address)
* any transaction or error message shown


# What is the Stone Wallet referral program?

The Stone Wallet referral program allows you to earn a share of the fees generated by users you invite.

When someone signs up using your referral link or code and uses Stone Wallet, you receive a portion of the commission generated from their activity.

***

### How much can I earn?

You can earn 50% of the commission generated by your direct referrals.

This applies to eligible activity within Stone Wallet, such as payments or other fee-generating actions.

***

### How do I invite others?

You can invite others by sharing:

* Your referral link
* Your referral QR code

These can be shared online or in person.

***

### When do I receive my commission?

Referral commissions are calculated and settled at the end of the month.

Once settled, they become available for you to claim in the app.


# Why was I charged but payment failed


# Earn

Within StakeStone’s Crypto-native Neo Bank, the Earn module (Yield Layer) serves as the central bridge connecting&#x20;onchain assets with underlying yield sources. The Earn Module leverages StakeStone's yield infrastructure to empower users' cryptocurrency holdings with institutional-grade yield opportunities. Currently, Earn Module provides services for&#x20;

* STONE (ETH)
* STONEUSD (Stablecoins)
* STONEBTC (BTC)


# STONEUSD

STONEUSD is a stablecoin yield service within StakeStone 2.0's Neobank Earn module. It is a liquid, yield-bearing token that represents a user's share in a diversified fund of risk-adjusted, market-neutral strategies, empowering stablecoin holders with competitive returns. STONEUSD makes institutional-grade yield easily accessible to everyone.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FwrLTUDxU6iSViJsNY9cO%2Fimage.png?alt=media&amp;token=c03abf43-e49e-416a-b22d-829997e09994" alt=""><figcaption></figcaption></figure>

#### Underlying Strategy & Assets

STONEUSD is backed by a curated basket of low-risk, market-neutral strategies. The current portfolio primarily consists of several arbitrage strategies operated within CEXs (e.g., Binance).

This multi-strategy approach is continuously monitored and analyzed. The portfolio is dynamically adjusted based on market conditions and risk controls, aiming to deliver robust, low-risk, yet competitive stablecoin yields across various market environments.

#### In-Contract Exchange Rate & Yield Distribution

The STONEUSD Exchange Rate within its smart contract defines its USD value (e.g., 1 STONEUSD = X USD). This rate reflects the asset value of the underlying portfolio and is used for permissioned minting and redemption.

Yield accrues directly through the appreciation of this exchange rate. For example, if a user acquires STONEUSD when 1 STONEUSD = 1 USD, and the rate later appreciates to 1.1 USD, the 0.1 USD difference represents the user's earned yield.

The exchange rate is updated regularly to accurately reflect fund performance.

#### Market Price & Instant Liquidity

The Market Price of STONEUSD is its trading price on the open market. While it references the in-contract exchange rate, it is also influenced by supply, demand, and liquidity factors and may not always match it exactly.

StakeStone, in partnership with Native, provides enhanced instant liquidity via a Private Market Making (PMM) solution. This offers users more competitive pricing and execution certainty for larger trade sizes.

This PMM liquidity can be accessed directly through StakeStone's interface or via major aggregators.

#### How to Use STONEUSD

**Permissionless Swap (For All Users):**\
STONEUSD is freely tradable and transferable. Any user can buy or sell STONEUSD on the secondary market at the prevailing market price.<br>

**Permissioned Mint / Redeem (For Institutions & Whales):**\
Users and institutions requiring larger sizes or stronger price certainty can contact the StakeStone team. After completing KYC/KYB and obtaining whitelist access, they can mint STONEUSD at the contract rate. Redemptions are processed on a weekly basis.

#### Multi-Chain Availability

STONEUSD is deployed across multiple blockchains for easy integration into the broader DeFi ecosystem. Users can bridge their STONEUSD between supported chains directly via the dedicated Bridge page.

<br>


# A Deep Dive Into Traditional Banking

and it's breaking points

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2F6jXbsxfib8z6ob9Fh8Qe%2Fimage%20a.PNG?alt=media&amp;token=2d585c4e-6992-4899-988a-b2a804fcbf26" alt=""><figcaption></figcaption></figure>

The core functions of traditional banks can be grouped into three main areas:

* Custody: Safeguarding users’ funds through deposits and settlement services.
* Credit: Lending depositors’ money to borrowers through credit operations.
* Payments & Clearing: Facilitating the transfer of funds between different accounts and institutions.

These functions are, by nature, intermediary roles, relying on centralized banks and clearing institutions to operate. The above image illustrates how banks and clearing institutions currently collaborate in cross-border payment systems. However, the legacy system was designed as a patchwork of separate banks, each with limited trust and coordination, it inevitably starts facing inefficiencies that shape many of today’s banking challenges.

In the sections ahead, we take a holistic look at how traditional banking works—from its technology stack to its operational workflows— and the challenges they face today to illustrate why legacy rails are no longer capable of supporting the financial systems of the future.<br>


# An Expensive System by Design

The traditional banking system wasn’t built to be lean. Banks shoulder hefty operational expenses across IT infrastructure, compliance, staffing and branch networks, and the complex coordination costs of upstream and downstream industry chains. These costs ripple through the entire system, leading to two main challenges:

#### The Unbanked and Underbanked

Even in 2024, 21% of adults worldwide have no bank account. Many banks require minimum deposits just to break even on operational costs, effectively shutting out lower-income users. And for those who do have accounts, as many as 30–60% are underbanked, unable to access loans, remittances, or investment services without turning to alternative financial services.*(Source:* [*Lucidity Insights*](https://lucidityinsights.com/infobytes/over-34ths-of-adults-remain-unbanked-or-underbanked?utm_source=chatgpt.com)*)*

#### Friction Costs: A Hidden Drain on Profits&#x20;

In today’s banking landscape, every financial transaction carries a hidden layer of friction. Because each bank operates as a separate entity with limited mutual trust, funds must often pass through third-party clearinghouses to reach their destination. While this structure helps ensure security, it introduces complex and layered fee mechanisms. Businesses must absorb fixed fees, percentage charges, and intermediary costs, as well as hidden foreign-exchange losses.\
This is especially pronounced in cross-border payments, where currency conversion fees, bank processing charges, and card network fees stack on top of each other. The result is an opaque and unpredictable cost structure that makes accurate forecasting difficult and gradually eats into corporate margins, becoming a significant barrier to global business growth.


# Friction Costs: A Hidden Drain on Profits

In today’s banking landscape, every financial transaction carries a hidden layer of friction. Because each bank operates as a separate entity with limited mutual trust, funds must often pass through third-party clearinghouses to reach their destination. While this structure helps ensure security, it introduces complex and layered fee mechanisms. Businesses must absorb fixed fees, percentage charges, and intermediary costs, as well as hidden foreign-exchange losses.\
This is especially pronounced in cross-border payments, where currency conversion fees, bank processing charges, and card network fees stack on top of each other. The result is an opaque and unpredictable cost structure that makes accurate forecasting difficult and gradually eats into corporate margins, becoming a significant barrier to global business growth.


# Efficiency Bottlenecks

Today’s banking infrastructure remains deeply tied to manual workflows and legacy operations, making speed and efficiency hard to achieve at scale. Take international remittances as an example: Transfers usually take 1 to 5 business days to clear. But with added compliance steps, multiple intermediary banks, or complex routing, that timeline can stretch to 1–2 weeks.

A closer look at what drives these delays reveals a complex web of structural constraints:

| Factors                                                               | Effects                                                                                                                                                                        |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Initiation Time/Bank Cut-Off Times                                    | Transfers submitted after the bank’s daily cut-off time are rolled over to the next business day.                                                                              |
| Number of Intermediary/Correspondent Banks                            | If there is no direct channel between the sending and receiving banks, the transfer must pass through multiple intermediary banks, and each step introduces additional delays. |
| Currency Conversion & Forex                                           | When currency conversion is involved, settlement often depends on FX market hours, which can postpone the final settlement.                                                    |
| Compliance & AML                                                      | Large or higher-risk transfers are more likely to trigger manual reviews, significantly increasing processing times.                                                           |
| Receiving Bank Processing Speed                                       | Even after funds reach the receiving bank, internal clearing and crediting checks can further delay the time until the funds are available.                                    |
| Public Holidays/Weekends/Differences in Working Days Across Countries | Cross-border transfers are especially vulnerable to differences in weekends and public holidays across countries; one non-working day can halt the entire chain.               |
| Banking Infrastructure and Legal Frameworks of Sending/Receiving Bank | Mature financial systems process transactions more quickly, while stricter or less mature infrastructures tend to cause slower settlements.                                    |

All of this points to one conclusion: the inefficiencies built into today’s banking system are structural, not accidental. Without system-level upgrades and process overhauls, no amount of fine-tuning will make the system truly faster.


# Disparities in Access to Global Financial Opportunities

Inequality in financial access plays out on two fronts. In financially developed regions, premium investment opportunities are largely reserved for the wealthy. Institutions such as private banks, hedge funds, private equity firms, and family offices typically set high investment thresholds, pricing out ordinary investors. Those with moderate wealth often find themselves locked out of top-tier asset allocation opportunities, deepening the wealth gap over time.\
Meanwhile, in less developed markets, weak infrastructure and limited professional capacity results in fewer options for diversified, high-quality investment channels. Many are left to rely solely on basic savings methods or risky alternatives. Incomplete regulatory frameworks and unfavorable market conditions also make it difficult to attract capital and innovative financial products, further deepening the global divide in financial opportunity.


# Why Traditional Banking Wasn’t Built for AI

Banking was built for a different era, one of slow, manual processes and overnight reconciliations. The AI and machine economy couldn’t be more different.\
On the technical side, most banks still run on COBOL-based mainframes and rely on batch processing, a model built for nightly reconciliations, not real-time execution. Bank data is scattered across siloed business lines, inaccessible to AI models that depend on clean, structured, real-time inputs. Scaling centralized infrastructure to meet AI’s compute needs requires expensive, slow-to-deploy physical upgrades.\
On the operation side, manual processes still dominate in traditional banking. Loan approvals, compliance checks, and risk management all rely heavily on human intervention. Transaction flows are complex and involve third party intermediaries, making them poorly suited for instant M2M payments. Even the way banks are designed—around occasional, high-value transactions—runs counter to the high-frequency, real-time, microtransaction patterns of the IoT economy.\
Legacy banking was built for a world of low-frequency, high-value, human-led batch operations. The AI era runs on speed, scale, and automation. This structural mismatch makes it difficult for traditional banking systems to operate efficiently in the age of AI and machine intelligence.

![](https://wsgpm1y4ctjb.sg.larksuite.com/space/api/box/stream/download/asynccode/?code=NDc5ZWIzNGVlZjRhODVlYWZmYWRjOTA1ZjI1OTIwYWRfV2VmbDlDUVA0RGFoUDdLdlVPSmpzVklXSHQ5YnZmWkdfVG9rZW46TVdiZWJlT3p0bzJZS0d4aUZya2xhOU5GZ2RjXzE3NjMwOTczMDU6MTc2MzEwMDkwNV9WNA)

The chart above highlights just how different traditional banking is from the AI and computer-driven economy across six dimensions:

* Transaction Frequency: Banks are built for low-frequency usage; machines demand constant, high-frequency interactions.
* Transaction Size: Traditional banking focuses on large, batch transactions, while the AI/machine economy is characterized by small, instant payments.
* Processing Model: Banking still depends on batch cycles; AI requires real-time processing.
* Human Dependence: Legacy workflows lean on manual approvals; the machine economy thrives on automation.
* Data Structure: Banks lock data in silos; AI needs open, connected data environments.
* Scalability: Traditional infrastructure expands slowly; the machine economy expects rapid, on-demand scale.

In short, banking was built for a world of low-frequency, high-value, human-led batch operations. The AI economy runs on the opposite logic — high-frequency, small-value, real-time, automated flows. The design logic of centralized banking is almost the mirror opposite of what the AI era requires.


# Banking 2.0: The Crypto-Native Upgrade

The Internet once reshaped how we imagine banks. If traditional banks had never existed, how would we design a bank fit for the digital age? This inspired the emergence of neo-banks like Revolut and Monzo, digital platforms that improved traditional banking through better UX and efficiency. Yet, their core architecture remained tied to the legacy banking system.

Today, blockchain evolution prompts StakeStone to ask the same question: without legacy banks, how would we build a future-ready and decentralized financial system for the blockchain era?

**StakeStone’s answer is the Crypto-native Neo Bank** —a blockchain-based financial infrastructure that replaces centralized intermediation with programmable, trustless systems.

• Settlement Layer: High-performance blockchain networks provide native clearing and settlement.

• Identity Layer: Intuitive identity solutions enable fully self-custodied on-chain accounts.

• Interaction Layer: Account Abstraction supports native on-chain smart operations.

• Intelligence Layer: With AP2(Agent Payments Protocol) and x402, StakeStone's system is fully compatible with AI agents and machine payments.

This architecture empowers both human and machine agents to transact globally with real-time, low-cost, and secure settlements, forming the cornerstone that we believe as the future of an autonomous, borderless financial era.


# Account & Identity Layer

A key pillar of a Crypto-native Neo Bank is a reimagined Account and Identity infrastructure, the foundation of a new financial paradigm. Built on frontier innovations such as EIP-7702, Social Login, and Gasless infrastructure, it redefines what a financial account can be.\
These modules collectively define the architecture of future financial accounts, evolving beyond traditional wallets to support a shared financial account system across both human and AI agents. Our Account & Identity layer ensures compliance and security while delivering a truly frictionless financial experience.

#### EIP-7702: Smart Functions for Self-Custodied EOAs

EIP-7702 is a key proposal in Ethereum’s Account Abstraction roadmap. It allows traditional Externally Owned Accounts (EOAs) to temporarily gain the capabilities of smart contract accounts without changing addresses or migrating assets.Through EIP-7702, user accounts can dynamically load smart logic within a single transaction, enabling contract-level permissions and automated execution. This evolution transforms accounts from passive asset containers into programmable financial agents capable of policy enforcement and intelligent responses.Within StakeStone's Crypto-native Neo Bank architecture, EIP-7702 upgrades *static wallet accounts* to *active entities*, enabling:

* Dynamic feature upgrades: enable smart contract functionality in any transaction without asset migration.
* Programmable security: integrates multisig, limits, and freeze policies at the account level.
* Automated asset management: trigger portfolio reallocation based on preset conditions (e.g., yield or FX changes).
* Institutional-grade accounts: enable role-based authorization, risk controls, and compliance.

EIP-7702 thus serves as a cornerstone for the Crypto-native Neo Bank, enabling smart account capabilities and programmable finance without compromising self-custody.

#### Social Login: Frictionless User Onboarding via Identity Abstraction

Web3 wallets traditionally require users to manage seed phrases and interact with complex transaction flows, posing as a major usability barrier. Social Login solves this by integrating Web2 authentication (Google, Apple ID, X, etc.) with MPC- or smart-contract-based key management, delivering a seamless, self-custodied blockchain experience.As a core module of StakeStone’s Identity Abstraction Layer, Social Login provides:

* Frictionless account creation: one-click onboarding using existing social credentials.
* Private Key fragmentation: private keys are split and stored via distributed cryptography.
* Accounted = Identity: on-chain accounts double as user identities for built-in KYC/AML support.
* Privacy-preserving compliance: zero-knowledge proofs enable verifiable compliance without data exposure.

By abstracting away blockchains technical barriers, Social Login enables true mass adoption, bridging the simplicity of Web2 with the autonomy of on-chain finance.

#### Gasless: Frictionless Transactions

Conventional blockchains require users to hold native tokens for gas fees, a requirement that not only raises the entry barrier but also limits mainstream usability. Gasless transactions solve this by using relayers or protocol-level gas sponsorship, enabling users to interact on-chain without needing to handle network fees.Within the StakeStone architecture, Gasless transactions integrate deeply with EIP-7702 and Social Login, forming a complete *Identity–Account–Transaction* loop:

* Account-level gas abstraction: smart accounts automatically sponsor or manage gas on behalf of the user, enabling zero-friction interactions.
* Multi-token fee abstraction: users can pay fees using any stablecoin or other cryptocurrencies, not just the native token of a given chain.
* Optimized for institutions & IoT: ideal for high-frequency, low-value transactions such as retail micro-payments and machine-to-machine settlements.
* Seamless UX: users onboard, transact, and manage assets with zero exposure to blockchain internals.

By abstracting away gas fees while maintaining transparency and composability, Gasless transactions bring Web2-grade usability to Web3-native finance.


# Yield Layer

Within StakeStone’s Crypto-native Neo Bank, the Yield Layer serves as the central bridge connecting onchain assets with underlying yield sources.Our Yield Layer supports two implementation paths based on asset type:

* For non-yield-bearing assets such as BTC and stablecoins, StakeStone employs a combination of smart contracts, custodial infrastructure, and multi-exchange strategies to convert deposits into onchain, verifiable yield-bearing tokens: STONEBTC and STONEUSD. Automated mechanisms manage yield distribution, NAV updates, and synchronized settlement across various execution layers (L2s, centralized exchanges, and custodial venues).
* For natively yield-bearing assets such as ETH, StakeStone utilizes staking and restaking protocols through smart contracts to generate native onchain yield. Returns are represented and settled via STONE (StakeStone Ether), a yield-bearing token.

#### STONEUSD/STONEBTC

#### 1. Deposit & Mint

After completing on-chain KYC/KYB verification, users can deposit stablecoins (e.g., USDC, USDT) or wrapped BTC (e.g., BTCB) into their yield-bearing accounts.All deposit transactions are routed through the StakeStone Router Contract, which aggregates incoming funds and allocates them to the corresponding Custody Wallet and Strategy Pools based on the system’s yield optimization logic.Once the deposit is confirmed, the smart contract executes the minting process:

* Based on the current Exchange Rate (denoted as R), the contract mints a corresponding amount of LP tokens (STONEUSD or STONEBTC) serving as yield-bearing certificates.
* The user’s holdings of STONEUSD or STONEBTC represent their share of the total yield pool, redeemable at any time.
* The Exchange Rate updates periodically based on realized yields from custody and execution layers, forming a transparent and traceable on-chain yield record.

#### 2. Delegation & Strategy Execution

Once funds enter the custodial layer, the system automatically allocates them across multiple yield sources according to predefined strategies:

* Ceffu Custody Accounts: Serve as the primary liquidity pool, receiving and redistributing funds from multiple users.
* Exchange Accounts (Binance, OKX, Bybit, etc.):
  * Funds are mirrored automatically from custody to exchange sub-accounts (e.g., A-1, A-2, A-3, B-1, B-2, B-3…).
  * Each sub-account may correspond to a distinct strategy execution unit, presently dedicated to neutral arbitrage strategies.
* Yield Distribution Logic:
  * Arbitrage partners or exchanges periodically update performance metrics, including PnL, interest, and fees.
  * Smart contracts perform scheduled on-chain settlements to distribute yields proportionally and transparantly.

Following each settlement period, the system issues an Exchange Rate Update, updating new data to the main contract, ensuring STONEUSD / STONEBTC values are accurately reflected in the next cycle.

#### 3. Withdrawal & Settlement

When a user initiates a withdrawal, the system redeems assets based on the latest Exchange Rate and coordinates onchain settlement by recalling funds from custody and exchange accounts.

* Withdrawal Request & Verification:
  * &#x20; Users submit withdrawal transactions via smart contract. The system verifies their KYC status, the STONEUSD / STONEBTC balance and compliance limits, and generates a unique Request ID for the redemption order.
* Exchange Rate Calculation & On-chain Snapshot:
  * &#x20; The contract determines the redemption amount using the current Exchange Rate and performs an onchain snapshot to ensure consistency between the redemption value and the current accounting cycle.
* Custody Undelegation & Fund Return:
  * &#x20; The backend server calls custodial platform's (e.g., Ceffu) APIs to execute undelegation of funds. Exchange sub-accounts (Binance, OKX, etc.) automatically close market-neutral arbitrage positions, after which funds are transferred back to the main custodial wallet.
* Settlement & Distribution:
  * &#x20; Custodians send back yield and fund settlement data to the system, which then issues an Exchange Rate Update. The smart contract burns the corresponding STONEUSD / STONEBTC and releases the equivalent underlying assets to the user’s wallet.
* Settlement Archival & Risk Synchronization:
  * &#x20; The backend records a settlement snapshot for the current cycle, while the risk management module updates liquidity pool and liquidity coverage ratio, completing the redemption feedback loop.

#### 4. Cross-layer Coordination & Safeguards&#x20;

The Yield Layer within StakeStone’s Crypto-native Neo Bank is a multi-layered, multi-strategy execution network designed for both efficiency and transparency.

* L1: STONE token issuance, Exchange Rate and Settlement;
* L2/ App Chains: Distribution of yield bearing tokens through liquidity pools;
* Custodial & Exchanges: Yield generation and asset security;
* AI Risk Engine: Continuously monitors fund movements and yield volatility within custody accounts.

This design allows StakeStone to operate a multi-layered yield generation network with transparency on-chain, efficiency off-chain, and seamlessly coordinated across all layers.

### STONE (StakeStone Ether)

Within StakeStone’s Crypto-native Neo Bank architecture, STONE (StakeStone Ether) serves as the yield-bearing token for Ethereum-native assets (ETH).Unlike STONEUSD and STONEBTC, which depend on custodial infrastructure and cross-layer settlement, STONE’s yield is generated onchain from staking and restaking protocols within the DeFi ecosystem. The entire process, from yield generation and distribution to Exchange Rate synchronization, is executed onchain through smart contracts.

1. #### **Deposit & Mint**

Users deposit ETH directly into the StakeStone smart contract, where the StakeStone Vault acts as a liquidity buffer, temporarily receiving deposited ETH to optimize capital utilization and operational efficiency.Upon deposit, the protocol automatically executes the minting of STONE, while the deposited ETH remains in the Vault. Once the aggregated deposits meet the deployment threshold, StakeStone Vault allocates and deploys funds to various Strategy Pools:

* The number of STONE (StakeStone Ether) tokens minted is determined by the current Exchange Rate (R-value);
* STONE represents the user’s share of the ETH yield pool and remains redeemable at any time;
* The Exchange Rate updates periodically to reflect underlying staking and restaking yield rate changes, maintaining an on-chain yield record.

This architecture guarantees that deposits begin earning yield upon deposit while preserving transparency and smart contract security.

2. #### **Delegation & Strategy Execution**

Once assets are deployed to the Yield Layer, the system distributes funds among multiple Strategy Pools based on pre-determined allocation logic set by the on-chain governance module OPAP, balancing yield generation and security:

* Base Staking Layer:
  * &#x20; ETH is delegated to leading Ethereum staking pools or validator operators to earn native PoS rewards and transaction fees.
* Restaking Layer:
  * &#x20; By integrating restaking protocols such as EigenLayer and Symbiotic, ETH is restaked into distributed security networks to obtain additional yield.
* Yield Settlement & Distribution:
  * &#x20; Yield data from each Strategy Pool is automatically consolidated and reported to the main contract, which performs unified settlement and produces an Exchange Rate Update.
* OPAP Strategy Mechanism:
  * &#x20; The underlying yield strategy of STONE is managed entirely by the On-chain Proposal Allocation Protocol (OPAP) to ensure transparency and decentralized governance. Any modification to base strategies requires approval through a vote by STONE holders before implementation.

3. #### **Withdrawal & Settlement**

When a user requests to redeem STONE, the protocol calculates the amount of ETH to be withdrawn based on the current Exchange Rate and proceeds through the settlement logic:

1. The contract determines the redeemable asset value according to the Exchange Rate. If the Buffer Pool balance is sufficient, the user can use the “Instant Withdrawal” option to withdraw ETH immediately from the buffer pool.
2. If the Buffer Pool balance is insufficient, the user can initiate a “Request Withdrawal”. The withdrawal request becomes claimable after the protocol completes unstaking operations, secures sufficient redeemable liquidity, and finalizes the next settlement cycle. The user can then claim their withdrawal.
3. Whether "Instant Withdrawal" or "Request Withdrawal", the contract burns the corresponding STONE and releases an equivalent amount of ETH, including both principal and accrued yield.
4. All settlement actions and records are executed fully on-chain, remaining traceable, verifiable, and auditable.


# AI & Machine Payment Layer

As AI and IoT technologies become ubiquitous, future economic activities will no longer be driven solely by humans but increasingly by Intelligent Agents that can execute and settle transactions automatically.The AI & Machine Payment Layer of StakeStone’s Crypto-native Neo Bank is designed precisely for this purpose: it enables every AI, device, or algorithm to possess a verifiable identity, a funding account, and payment capabilities, allowing them to function as Autonomous Economic Actors within the financial system.This layer integrates next-generation machine payment protocols such as Google’s AP2 (Agents-to-Payments Protocol) and Coinbase’s x402, forming a fully automated loop from Agent Decision to On-chain Settlement, and establishing the foundational layer of true MachineFi (machine finance).In StakeStone’s Crypto-native Neo Bank architecture, the system supports:

* **AP2** **(Agents-to-Payments Protocol):** Defines how intelligent agents generate, transmit, and sign payment intents.
* **x402** **(HTTP-based Payment Protocol):** Provides a standardized payment authorization and verification channel, enabling onchain settlement and micropayments without relying on traditional centralized account infrastructures.

**Core Applications:**

1. **Agent Identity Layer**
   1. Each AI or IoT device is assigned an onchain account (e.g., EOA) that registers a unique identity, which can become a smart account through EIP-7702.
   2. This identity is bound to the device’s StakeStone bank account, permission policies, and onchain compliance modules (ZK-KYC / AML), forming an Identified Machine Account (IMA) with verifiable credentials and programmable access control.
2. **Payment Intent via AP2**
   1. The Identified Machine Account (IMA) can create an Intent Mandate via the AP2 protocol, authorizing automated payment actions under predefined conditions.
   2. Based on triggering pre-authorization conditions or merchant-side quotations, the AP2 framework generates a Cart Mandate.
   3. After two-way verification within the StakeStone system, the data is packaged into a standardized Payment Intent, which includes amount, recipient, execution conditions, contextual data, and execution logic.
3. **Execution & x402**
   1. A Payment Intent can be executed either directly by an authorized StakeStone smart contract or sent to an x402 facilitator for offchain or hybrid settlement.
   2. The x402 facilitator verifies the signatures and authorization, executes the payment settlement (or forwards the transaction to onchain execution), and returns an HTTP 200 response to confirm payment completion and service accessibility.
4. **Compliance Feedback Loop**
   1. Every payment automatically triggers onchain compliance verification through ZK-KYC / AML RuleSets, ensuring audit visibility for all machine-to-machine transactions.
   2. Transaction and settlement states are synchronized in real time with StakeStone’s Risk Control System and Regulatory Interfaces, achieving Compliance-as-Code through protocol-level enforcement.

Through the combination of AP2 and x402, StakeStone’s machine accounts can not only perform settlements within its own system but also interoperate with mainstream enterprise-grade payment networks, achieving a Unified Flow between human and machine accounts.


# Fee & Settlement Layer

#### Payment Abstraction: Multi-Asset Settlement & Fee Neutrality

While Gasless transactions address the user-side fee barrier, Payment Abstraction redefines how fees are sourced and settled within the system.Legacy blockchains restrict gas payments to native tokens (e.g., ETH), creating friction in cross-chain and multi-asset ecosystems and forcing users and institutions to constantly perform token swaps and top-ups, creating liquidity fragmentation and a discontinuous user experience.In StakeStone’s Fee Layer, Payment Abstraction—built atop Account Abstraction and relayer infrastructure—makes the fee source programmable. Any verified asset can act as gas, enabling a unified multi-asset payment system under a single account.Key Components:

* Multi-Asset Gas Payments: Users can pay network fees using stablecoins (USDC, DAI, CUSD) or CBDCs, instead of being restricted to native tokens.
* Intelligent Exchange Routing: An embedded router uses oracle-based FX rates for real-time conversions and accurate settlement.
* Sponsored Fee & Incentive Mechanisms: Institutions, protocols, or merchants can sponsor gas fees, thereby supporting B2C and B2B incentive models.
* Cross-chain Account Interoperability: One account can execute payments and transfers across multiple chains without switching mainnets or asset types.

This abstraction framework brings cross-chain neutrality and asset-agnostic settlement to StakeStone’s neo-bank architecture, transforming transaction fees into a programmable parameter that adapts to any asset, network, or participant.

#### Settlement Layer: Layered Settlement Architecture

The settlement layer of StakeStone’s Crypto-native Neo Bank is designed to support diverse capital flow scenarios, including:

* Account transfers and balance management between user accounts;
* DeFi/yield product Exchange Rate updates;
* Cross-chain and multi-asset liquidity transfers;
* Automated micropayments between AI agents.

Unlike traditional banks, the asset structure of a crypto-native bank is multi-sourced and contains complex liquidity routes. A single, uniform settlement logic cannot cover all asset types and transaction models. StakeStone therefore implements a layered settlement model based on asset characteristics and transaction scenarios.

**Balance Settlement Layer**

Handles transactions such as real-time transfers between accounts, payments, and settlements. Depending on transaction size, two blockchain settlement environments are required:

1. High-value, low-frequency transactions: settled directly on Ethereum L1.
2. Low-value, high-frequency transactions: processed in high-performance execution environments (e.g. L2 rollups/appchains) to achieve:
   1. Real time usability for frequent payments, P2P payments, merchant settlements, and machine-to-machine micropayments;
   2. Cost efficiency: reduced transaction costs through L2/app-chain gas efficiency, Gasless fee abstraction, and batch processing mechanisms.

**Yield & NAV Settlement Layer**

Unlike the Balance Settlement Layer, this component of StakeStone’s Crypto-native Neo Bank focuses on how yield-bearing tokens maintain accurate NAV updates on L2 or high-performance appchains.To achieve this, the settlement of yield certificates adopts an L1–L2 / appchain dual-layer coordination model:

* L1 — Sole source of settlement and pricing
  * The pricing of yield tokens are calculated and updated exclusively on Ethereum L1, serving as the single authoritative source for price formation.
  * For large-value transactions, users can directly invest or redeem yield-bearing tokens based on native L1 pricing, with yield settlement completed on L1.
* L2 / Appchains — Retail distribution through swap
  * Yield-bearing tokens bridged to L2/appchains are swapped by retail users via DEXs.
  * The purchase and redemption prices of these tokens are determined either by DEX liquidity or directly quoted by RFQ (Request for Quotation) providers.
  * The low transaction costs and high execution efficiency of L2/appchains allow yield-bearing tokens to reach a broader retail market, supporting smaller investors.


# Compliance & Security Layer: Embedded Regulation & Transparancy

In StakeStone’s Crypto-native Neo Bank, the Compliance & Security Layer elevates onchain finance from self-governing automation to a state of being regulatable, auditable, and verifiable.\
By embedding compliance logic, risk controls, and audit modules directly into the protocol core, this layer implements regulation by design—where oversight and innovation coexist at the technical level.\
Our goal is to establish a globally compliant yet transparently decentralized financial infrastructure, maintaining both regulatory alignment and crypto-native self-sovereignty.

#### Onchain KYC/AML Module: Compliance Proof with Privacy

Traditional financial systems rely on manual processes or centralized databases for identity verification and anti–money laundering monitoring. StakeStone replaces this model with an On-chain Compliance Identity Layer that uses zero-knowledge proofs to enable privacy-preserving compliance verification.

* ZKP-based Identity Verification:
  * &#x20; Certified KYC providers validate user identity and risk profiles, issuing a ZK Compliance Credential. When interacting on-chain, users only present a proof, without revealing any plaintext personal information.
* Multi-level Compliance Mapping:
  * &#x20; Each account carries a dynamic compliance status indicator (Compliant / Restricted / Pending), written directly into the account layer. This integrates seamlessly with EIP-7702's flexible authorization system, enabling transaction-level permission control.
* Cross-chain / Cross-jurisdiction Interoperability:
  * &#x20; KYC/AML credentials can interoperate across multiple networks through bridges and cryptographic signatures, allowing StakeStone to maintain compliance across different countries and regulatory bodies.

This approach establishes a neo-bank version of “Know Your Wallet (KYW)”, ensuring that every account possesses a verifiable compliance identity without compromising user privacy

#### Programmable Regulatory Interface: From Manual Reporting to Automated Compliance Execution

StakeStone’s Crypto-native Neo Bank implements a Regulatory API Layer, enabling regulation compliance to be embedded directly into the banking system as executable code, rather than relying on reports or manual verification.

* API-level Regulatory Integration:
  * &#x20; Regulatory authorities or compliance nodes can define rules via smart contract APIs, such as cross-border transfer limits, restricted address lists, and reporting intervals. Enabling the system to automatically validate compliance prior to transaction execution, ensuring preemptive enforcement.
* Automated Compliance Data Reporting:
  * &#x20; Transaction and account data are encrypted and synchr to designated regulatory endpoints, guaranteeing real-time availability and tamper-proof compliance records.
* Compliance-as-Code:
  * &#x20; Regulatory logic is parameterized and upgradeable, forming an evolving compliance framework where authorities from different jurisdictions can deploy their own rule templates on a shared protocol foundation.

This mechanism transforms regulation from an external oversight function into an intrinsic system capability—

> **Regulation becomes protocol; compliance becomes automatic.**


# Conclusion & Outlook

Traditional banking systems are built upon centralized trust and multi-layered intermediaries, resulting in high costs, inefficiency, imbalance, and an overall inability to adapt to the era of intelligent automation.

Over the past decade, the rapid evolution of blockchain technology has prompted a fundamental question: *if the banks of the past had never existed, how would we rebuild them for the future using today’s most advanced blockchain technologies?*

StakeStone 2.0—our Crypto-native Neo Bank—was designed as a systematic answer to that question, reimagining the foundations of banking for the decentralized, machine-integrated economy of tomorrow.

### I. **Addressing High Costs: From “Human Trust” to “Code Trust”**

The high operating costs of traditional banks stem from their dependence on manual processes, compliance overhead, IT infrastructure, physical branches, and multi-layered settlement structures.StakeStone 2.0 replaces these inefficiencies with **Account Abstraction (EIP-7702)**, **Gasless transactions**, and **Social Login**, enabling **self-custodied accounts with** **automated trust through smart contracts and** **zero-friction onboarding**.

* **Account-as-the-Bank:** Users hold their own onchain accounts—funds no longer require third-party custody.
* **Gasless Transactions:** Fees are abstracted away, creating a Web2-level user experience.
* **Smart Account Logic:** Multi-signature, spending limits, automated yield management, and risk controls are all executed by code instead of manual approval.

For the first time, the cost of trust in banking transforms from human to computational, turning users from recipients of service into autonomous financial actors.

### II. **Addressing Inefficiency: From “Batch Settlement” to “Real-time Settlement”**

Traditional banks rely on multi-tiered clearing processes and manual reconciliation for interbank and cross-border transactions, making T+N settlements the norm. These legacy systems depend on end-of-day batch processing, which introduces latency and operational friction.

StakeStone 2.0 replaces this with a **layered settlement architecture** that defines differentiated settlement logic based on asset type and transaction scenario. In this model, each transaction achieves settlement instantaneously, and each settlement equals final confirmation, achieving true real-time settlement.

As a result, cross-border payments, peer-to-peer transfers, and machine-to-machine micropayments can now be executed with near-zero latency, redefining financial efficiency for the onchain era.

### III. **Addressing Inequality of Opportunity: From “Closed Access” to “Open Inclusion”**

Traditional banks divide the world into those who are served and those who are excluded, constrained by account requirements, regional barriers, and capital thresholds.\
StakeStone 2.0, through our onchain Yield Layer, enables anyone to participate in the global yield network with minimal entry barriers. Because the marginal cost of providing global financial services through code is near zero, the Crypto-native Neo Bank model makes universal financial inclusion possible for the first time.\
Regardless of geography or economic condition, every individual and institution can now participate equally within the same yield ecosystem, accessing opportunities once limited to a privileged few.

### IV. **Addressing Data Silos and AI Incompatibility: From “Human Decision” to “Intelligent Collaboration”**

Traditional banking architectures are closed, fragmented, and lack real-time processing or open interfaces, making them ill-equipped to support emerging financial scenarios such as AI-driven autonomous decision-making and machine-to-machine (M2M) settlement.Legacy operational logic still assumes that *“customers occasionally perform transactions”* rather than *“intelligent agents continuously interact and transact,”* leaving them fundamentally misaligned with the machine economy.StakeStone bridges this gap through the integration of AP2 (Agents-to-Payments Protocol) and x402, building an AI & Machine Payment Layer that enables every AI, IoT device, or algorithm to possess an independent identity and programmable payment capability.

* **AP2 defines payment intent:** AI agents automatically generate Payment Intents based on task objectives and resource requirements.
* **x402 provides authorization and secure settlement:** Built on the HTTP 402 status code, x402 offers a standardized payment authorization and validation channel. It receives and verifies Payment Requests from AP2, then executes onchain settlements or calls Custody APIs for fund transfers through designated facilitators.
* **Gasless + Compliance Module:** Relay services sponsor transaction fees, enabling fully automated and auditable agent transactions with integrated regulatory traceability.

AP2 manages payment intent and authorization logic, while x402 oversees verification and settlement. Together, they embed autonomous intelligence into StakeStone accounts, enabling them to make independent decisions and execute transactions, where AI and human accounts collaborate seamlessly within the same financial stack, fully aligning with the machine economy.

### V. **Addressing Regulatory Complexity and Opacity: From “Manual Reporting” to “Compliance-as-Code”**

StakeStone 2.0’s **Compliance & Security Layer** embeds **r**egulatory logic directly into the protocol layer through its **ZK-KYC/AML module** and **Programmable Regulatory API Layer**, ensuring that compliance and innovation coexist without conflict.

* **Zero-Knowledge Compliance:** Identity legitimacy is verified without exposing private information.
* **Embedded Regulatory APIs:** Compliance rules are executed directly as code, automatically intercepting non-compliant transactions.
* **Cross-Jurisdiction Recognition:** Encrypted credentials and transaction records are portable across networks, enabling multi-national regulatory interoperability.

Compliance is no longer an external burden but a native attribute of the system itself.StakeStone makes “Regulation as Protocol, Compliance as Execution” an onchain reality.

### **Toward the Bank of the Future: A Public Network for Global Value Flow**

What StakeStone is building is not a traditional financial intermediary dependent on manual processes and centralized systems, but a **new kind of Crypto-native Neo Bank** — a **financial infrastructure** rooted in **blockchain-based trust**, powered by **intelligent accounts**, and defined by **machine-to-machine interoperability**.When human and machine accounts share the same economic stack, and when yield, settlement, clearing, and governance all take place on a single open ledger, the bank is no longer merely a human-centered service institution — it evolves into a public network for global value flow.

> **StakeStone’s Vision**
>
> To make finance as open as the Internet,And let value flow as freely as information.This, is StakeStone’s answer to the future of banking.


# Appendix

### **R Value Calculation Formula for STONEUSD / STONEBTC**

To ensure transparency and consistency in yield distribution, NAV calculation, and locking cycles, the StakeStone Crypto-native Neo Bank adopts the following formula to calculate the R Value (Exchange Rate Ratio), which measures the periodic NAV change of yield-bearing tokens such as STONEUSD and STONEBTC:

![](https://wsgpm1y4ctjb.sg.larksuite.com/space/api/box/stream/download/asynccode/?code=ODUyYzg3YzE3M2FkMWFkYTg5MGExN2NjMzMwYTY2YzdfUHNwbnQ3R1VNWk1qQnk3UE9FRXQ2T1VnNVRKSEJjQ3RfVG9rZW46WHhEWWJlQmZ6b1p1QlZ4WE1RWGxZaEYxZ1pkXzE3NjMwOTg1NTE6MTc2MzEwMjE1MV9WNA)

| Parameter         |                                                                                                                                                                                                                                                                                                       |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `user_deposit`    | The user’s total cumulative deposit amount (gross inflow), retrieved in real time from onchain contract data.                                                                                                                                                                                         |
| `user_withdraw`   | The user’s total cumulative withdrawal amount (gross outflow), retrieved in real time from onchain contract data.                                                                                                                                                                                     |
| `user_profit`     | The user’s accrued yield, calculated by the system based on the results of strategy execution (including PnL, fees, and revenue sharing) and allocated to the user’s account.                                                                                                                         |
| `lp_amount`       | The total issued supply of STONEUSD (or other yield-bearing tokens), representing the total number of circulating yield tokens currently in the system.                                                                                                                                               |
| `lp_locked`       | The amount of STONEUSD in a locked state during the settlement process. Every Thursday (UTC), when user withdrawal requests are processed, the corresponding tokens are marked as locked.                                                                                                             |
| `lp_locked_value` | The value within the locked pool, calculated as lp\_locked × R (NAV at the time of locking). This value records the conversion ratio between STONEUSD and stablecoin for the given cycle. The system updates this figure every Thursday (UTC) and displays the current exchange rate on the frontend. |

#### **Parameter Definition & Framework**

* The R Value reflects the **periodic NAV fluctuation** of yield-bearing tokens and serves as the core variable for yield distribution and redemption settlement.
* The calculation logic is executed automatically each settlement cycle (typically once per week), ensuring that all user assets are settled accurately based on the latest exchange rate.
* If a locking operation occurs during a cycle, the corresponding tokens and values are temporarily excluded from the denominator to prevent short-term liquidity fluctuations from distorting NAV.
* All parameters are sourced from onchain verifiable data, ensuring that the entire computation process remains **transparent, auditable, and tamper-proof**.

#### **Snapshot & NAV Update Mechanism**

StakeStone performs its Snapshot & Settlement Cycle automatically every Thursday at 00:00 UTC, following this process:

1. Aggregate all user deposit, withdrawal, and yield records for the current cycle;
2. Compute the new R Value;
3. Update the Exchange Rate for yield-bearing tokens such as STONEUSD and STONEBTC;
4. Publish an onchain snapshot and synchronize the results to the user interface.

This mechanism ensures fair yield distribution, transparent NAV confirmation, and cross-layer data consistency within each cycle, while also providing a unified NAV reference across the custody, settlement, and contract layers.

### Swap & Burn

The **Swap & Burn** mechanism is one of the core components of the StakeStone protocol, designed to achieve **STO value capture** and **market equilibrium**.By allowing users to exchange STO tokens for diversified assets held in the Treasury while burning a proportional amount of STO during each swap, the system establishes a self-regulating value model that provides both intrinsic backing and a market floor for the token.

#### Operational Mechanism

Holding **STO tokens** represents a potential claim on a proportional share of the Treasury’s assets. As the protocol grows and accumulates revenue, the Treasury expands with additional blue-chip crypto assets.When the implied asset value per STO in the Treasury exceeds the market price of STO, an arbitrage opportunity arises. Users can then restore market equilibrium through the following process:

1. **Buy STO on the open market:** When the STO market price falls below its implied Treasury value, users can purchase STO at a discount in secondary markets.
2. **Execute Swap & Burn:** Users submit their STO to the protocol for a swap. The system calculates their share of Treasury assets (e.g., ETH, BTC, or stablecoins) based on the Treasury’s NAV, and **permanently burns** the corresponding amount of STO after the swap.
3. **Realize profit and value convergence:** Users receive Treasury assets, while the STO supply decreases, driving the token’s market price back toward its intrinsic value range.

#### Economic & Market Impact

Within StakeStone’s tokenomics, the Swap & Burn mechanism performs three key functions:

* **Deflationary Pressure:** Each treasury swap permanently burns STO, reducing total supply and introducing a built-in deflationary effect.
* **Value Realization:** Users can convert STO into Treasury assets, creating a verifiable asset-backed intrinsic value for STO.
* **Soft Value Floor:** The arbitrage process establishes a natural price floor, as market participants continuously rebalance STO’s price relative to Treasury NAV.

#### Self-Regulation & Sustainability

The Swap & Burn design ensures that arbitrage activity not only benefits participants but also stabilizes STO price. Its key characteristics include:

* **Price Discovery:** Market behavior dynamically corrects token valuation, keeping STO prices anchored near Treasury NAV.
* **Organic Equilibrium:** Swap activity maintains a dynamic balance between Treasury growth and STO circulation.
* **Sustainable Value Support:** As the Treasury continues to accumulate assets, STO’s intrinsic value and scarcity strengthen in tandem, reinforcing STO’s long-term stability.


# Whitepaper 2.0

{% file src="/files/zhQ6npgU9VDu5eCjFl8A" %}


# Whitepaper \[KR]


# Whitepaper MiCAR

{% file src="/files/91IYf9AgpMw8elBdAHrE" %}


# Background

The Ethereum Shanghai upgrade heralds a new era for ETH, characterized by risk-free yields of underlying assets, and introduces a series of paradigm shifts that are reshaping the crypto landscape.

For institutions and individuals seeking stable returns, the yield generated by Ethereum’s PoS mechanism is undeniably compelling. At the same time, as new liquidity mining opportunities arise, it becomes challenging for users to forgo PoS rewards in favor of providing liquidity with ETH directly.

Furthermore, for the next generation of DeFi protocols, Liquid Staking Tokens (LSTs), which bear ETH staking yields, are emerging as the preferred choice for liquid assets. LSTs, based on Ethereum's native yields, and their derivatives, LRTs, are poised to become superior alternatives to ETH in the realm of liquidity reserves.

With the rise of emerging scaling solutions such as Layer2 and other blockchain networks, the demand for LST liquidity is set to surge, solidifying its importance in the evolving DeFi ecosystem.

### The Problem&#x20;

Ethereum's transition to Proof of Stake (PoS) has been hailed as a revolutionary step forward for the blockchain industry, promising a more sustainable and scalable network. However, despite its groundbreaking potential, significant structural challenges within the current market landscape have hindered the full realization of these benefits.

**For Stakers**

Individual stakers aim to secure risk-free staking returns. However, the growing opportunities for additional yield through liquidity provision are more likely to arise on Layer 2 solutions or blockchains other than Ethereum. Thus creating a dilemma where users must choose returns between providing liquidity (LP) or staking, thereby incurring opportunity costs.

LRTs provide users with innovative mechanisms to enhance capital efficiency by enabling them to restake their assets across multiple protocols, effectively allowing them to earn multiple streams of yield. However, due to the fragmented nature of liquidity across different LRT pools, users often encounter a complex and disjointed experience. The introduction of new tickers and the intricate processes involved in managing liquidity across multiple platforms add layers of complexity to the user journey.

**For L2s and other EVM-compatible blockchains**

Emerging blockchains will face greater challenges in acquiring sufficient ETH liquidity due to the need to cover the opportunity cost of the risk-free yield for migrating native ETH from the ethereum ecosystem to projects such as L2s and other EVM compatible chains for TVL. Notably, with the widespread adoption of restaking, the opportunity cost linked to the risk-free yield could reach up to 10% to 15%.

**For Developers**

Developers often encounter various hurdles when integrating LRTs, particularly due to the constant introduction of new tickers for various pools by the same project founders, which complicates integration efforts and leads to inefficiencies in both the user journey and developer workflows. The frequent changes in tickers create a fragmented and cumbersome development process, making it difficult to maintain a stable system.&#x20;

Integrating cross-chain ETH further exacerbates these challenges, as obtaining price feeds without relying on oracles is complex. Furthermore, rebase tokens, which algorithmically adjust their supply, are particularly difficult to integrate and pose significant obstacles to achieving true omnichain operations, adding another layer of complexity.

### The Solution: Yield Bearing Liquid Assets

StakeStone presents a comprehensive solution by introducing a yield-bearing liquid asset: STONE. STONE is designed to address the core issues faced by users, protocols, chains, and developers, creating a more efficient and seamless experience across the board.

#### For Stakers:

The introduction of liquid assets by StakeStone eliminates the traditional opportunity cost associated with choosing between liquidity provision and staking. Users no longer have to compromise between earning staking rewards or participating in liquidity pools.&#x20;

With these yield-bearing liquid assets, users can simultaneously earn optimized returns on top of the risk-free yield from staking. This innovation not only maximizes potential earnings automatically for users but also allows for the full utilization of liquidity within the relevant ecosystems.

#### For **L2s and other EVM-compatible blockchain**s:

robust,StakeStone simplifies the complex challenges of liquidity management and user acquisition that protocols and chains often face. By leveraging liquid assets, these ecosystems can more easily bootstrap liquidity and attract users, creating a more organic, robust, and sustainable environment for growth. The streamlined process reduces the barriers to entry for new projects and helps established protocols maintain a steady flow of liquidity, ensuring the stability and efficiency of the ecosystem.

#### For Developers:

For developers, StakeStone's STONE token serves as a rebalance token, offering a powerful tool for integrating liquidity and staking mechanisms within dApps. The STONE token's design facilitates omnichain functionalities, not only reducing the complexity of integrating rebase tokens but also providing a more sustainable infrastructure to be fully adaptable to the dynamic nature of the blockchain space.

In summary, StakeStone's yield-bearing liquid assets provide a holistic solution that addresses the key challenges faced by users, protocols, chains, and developers alike. With our liquid asset STONE, StakeStone is poised to play a pivotal role in the evolution of the blockchain ecosystem.


# Yield Bearing Liquid ETH

The vision of StakeStone from day one was not merely to create a staking pool or restaking protocol but to build a yield-bearing liquid asset that could withstand the challenges of time. Our solution introduces the concept of liquid ETH, and we believe the following criteria are essential to making an asset truly liquid:

* **Transparency**: Our non-custodial approach ensures complete transparency of underlying assets and returns. Much like MakerDAO, StakeStone is committed to building a fully on-chain asset that is governed on-chain, providing full visibility into staking routes.
* **True Liquidity**: StakeStone leverages deep and efficient omnichain liquidity, allowing for easy redemption with minimal price impact. Users can opt for instant withdrawals on any chain, enjoying the flexibility of no lock-up periods. Unlike other staking protocols, StakeStone's robust omnichain liquidity allows for instant withdrawals on all chains. Our innovative design allocates a portion of ETH dynamically to a separate underlying yield strategy—Native's PMM lending pool—enabling market makers to provide exit liquidity for STONE holders across multiple chains, ensuring optimal liquidity and yield generation.&#x20;
* **Omnichain Accessibility**: STONE and its price feed flow seamlessly across multiple chains, ensuring broad accessibility. This omnichain approach allows for dynamic adjustments and coverage of opportunity costs through an adaptive staking network, providing users with broad access, smooth transactions, and consistent price feeds across various chains.
* **Adaptability**: STONE is compatible with multiple consensus mechanisms, including PoS, Restaking, Decentralized Sequencing, AI, and more. Our unique modular architecture, which separates the minter contract from our strategy vault contract, enables adjustable underlying strategies and optimized yield source opportunities. This flexibility ensures that users can benefit from a variety of consensus mechanisms while maximizing their yield potential through tailored strategies.
* **Optimization**: With a decentralized portfolio strategy, liquidity is reallocated effortlessly, maximizing staking yields. Unlike traditional staking pools where users are tied to a specific fixed yield source, STONE holders benefit from the flexibility to switch underlying portfolios—for example, from Eigenlayer to Symbiotic, Ora, or other consensus mechanisms such as decentralized sequencing or DePIN.
* **Consistency**: Upgrading the smart contract or adjusting STONE’s underlying assets does not affect the circulating STONE, ensuring the token’s stability. This stability is supported by our modular architecture and rebalancing design, which facilitate seamless DeFi integration and reward yield accrual on L2, as well as both institutional and mass adoption. Liquidity providers only need to hold STONE or utilize it across various scenarios, including DeFi, IDO, IMO, INO, payments, and even as collateral on centralized exchanges, unlocking a wide array of CeDeFi use cases.

By building STONE to meet these criteria, we are setting the foundation for it to become the universal standard for liquid ETH, capable of thriving in a wide range of utility scenarios, empowering both user and protocol.&#x20;

Our goal is to make STONE not only a cornerstone of the DeFi ecosystem—one that embodies transparency, liquidity, adaptability, and stability, but also an asset for real world businesses and use case. We believe that with STONE, we are paving the way for the future of liquid assets, offering worldwide users unparalleled flexibility in complex DeFi journeys and everyday scenarios.


# How It Works

#### Overview

STONE is a non-rebase ERC-20 token that operates similarly to Lido's wstETH in terms of yield generation. As a non-rebase token, the numerical balance of STONE in your wallet remains constant; however, its intrinsic value in ETH increases over time due to accumulated staking yields.

For example, if user A deposits 100 ETH for 100 STONE, and after one year, the value of 1 STONE rises to 1.04 ETH, the user can withdraw 104 ETH from StakeStone using their 100 STONE.

The price of STONE is determined by the smart contract and is not influenced by DEX prices or information platforms like CoinGecko. This contract-based price is used for both deposits and withdrawals, ensuring users can always redeem their ETH according to the current STONE price in the contract. Users can view the STONE price for deposits and withdrawals on [StakeStone's dApp](https://app.stakestone.io/u/stake).

Additionally, STONE is an Omnichain Fungible Token (OFT) built on LayerZero, allowing it to be seamlessly bridged across different chains. StakeStone leverages LayerZero’s solutions to develop customized contracts, enhancing STONE’s cross-chain compatibility. The upcoming mainnet will utilize Polyhedra and zkBridge for bridging STONE accumulated within the Bitcoin ecosystem, further expanding our interoperability and usability.

**STONE’s address**

Ethereum Mainnet: 0x7122985656e38BDC0302Db86685bb972b145bD3C

Manta Pacific: 0xEc901DA9c68E90798BbBb74c11406A32A70652C3


# STONE Mechanism

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FMpfjz7BwNRP3h5TLYBeS%2FStructure.png?alt=media&amp;token=4e89cc16-f13b-4638-a18a-8fe9148fab5a" alt=""><figcaption></figcaption></figure>

### STONE Mechanism

Upon depositing ETH into StakeStone, the Minter contract mints STONE according to the exchange rate between ETH and STONE, as determined by our smart contracts, and sends the STONE directly to the user. Simultaneously, the deposited ETH is transferred to the StakeStone Vault, where it is held in reserve until deployment is triggered.

**Deployment Process**

Once the deployment is activated by the smart contract, the ETH in the StakeStone Vault is allocated to the Strategy Pool. This pool is composed of various underlying yield strategies, each proposed through OPAP. The distribution of ETH across these asset routes within the Strategy Pool is dynamic and rebalanced according to the allocation ratio determined by the Optimizing Portfolio and Allocation Proposal mechanism.

**Governance and Rebalancing**

The asset routes and its corresponding weight within the Strategy Pool is governed by STONE holders through [OPAP](#opap), if and when the STONE community agrees on a new asset route, it will then be added to our Strategy Pool.

**Execution and Management**

After ETH is allocated to the Strategy Pool, it is utilized according to the designated strategies. For example, ETH might be staked to mint stETH, which could then be re-staked into EigenLayer, or withdrawn from EigenLayer and returned to the StakeStone Vault, depending on the strategic needs. These operations are executed securely by a multi-signature setup controlled by trusted partners like Cobo and Coincover, ensuring both security and transparency.

**Utilizing STONE for Additional Yield**

The minted STONE can be used to generate extra yield through [STONE-Fi Pools](/stakestone/stone-fi/stone-pools). These pools allow STONE to be deployed across different chains via our cross-chain bridge, enabling users to earn LP rewards. Additionally, users have the option to lock their LP tokens within StakeStone's protocol to receive enhanced rewards, maximizing their returns while contributing to the ecosystem's liquidity and stability.

**Omnichain Liquidity & Instant Withdrawals**

Powered by Native's advanced liquidity infrastructure, StakeStone provides users and developers with seamless omnichain liquidity. Users benefit from instant, low-slippage withdrawals across any chain, while protocols can tap into strong, omnichain ETH liquidity through STONE's infrastructure. STONE not only ensures reliable exit liquidity across chains but also enables its use on any DEX without the need for deploying dedicated liquidity pools, allowing protocols to focus on development without the burden of bootstrapping initial liquidity.

### Components

#### StakeStone Vault

*Management of deposit, withdrawal and settlement*

The StakeStone Vault acts as a buffer for deposited funds, holding the ETH within the contract until the next settlement, at which point it is deployed to the underlying strategy pool.

The StakeStone vault is only permitted to send ETH to the Strategy Pool contract, and does not allow anyone to unilaterally withdraw ETH out of the vault. Any deposit or withdrawal of ETH from the Strategy Pool contract has to be passed through OPAP by STONE holders, and the team does not have control over these funds.

#### Minter

*Minting and burning of STONE*

The Minter function decouples STONE token minting from its underlying assets. This separation allows for adjustments to the underlying assets without affecting the circulation of issued STONE tokens, ensuring a higher level of token stability.

#### Strategy Pool&#x20;

*Whitelisted asset yield routes*

The strategy pool utilizes a whitelist mechanism governed by OPAP, ensuring high compatibility with various protocols and consensus mechanisms. Additionally, asset risks are isolated within each individual strategy route, effectively preventing cross-contamination of risks.

#### **OPAP**

*On-chain proposal to add new yield routes and optimize allocations*

For more detailed description, please refer to the [OPAP](#opap) section.


# Stake & Mint

When users deposit ETH into StakeStone, the minter contract immediately mints STONE, which is then sent to the users.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FeuO6a1Zw0fjePolB2kbg%2FScreenshot%202024-08-20%20at%2023.07.38.png?alt=media&amp;token=c2268846-ae59-4729-824b-e0c6154966c7" alt=""><figcaption><p>STONE Vault</p></figcaption></figure>

All deposited ETH will be staked, and the stETH is kept in StakeStone's strategy vault, with the potential for these stETH to be restaked into various strategy pools.&#x20;

It’s important to note that STONE itself is compatible with restaking by integrating restaked assets as underlying assets, rather than being used directly as the asset for restaking.

Please note that the underlying strategy pool for STONE is managed through a decentralised governance process ("OPAP") and may change with time. For the most up to date strategy vault, please check [the Portfolio & Allocation section](https://app.stakestone.io/u/portfolio-allocation); click here for more details on [OPAP](/stakestone/stone-eth/how-it-works/opap).


# Unstake & Omnichain Withdrawal

STONE is an Omnichain Fungible Token (OFT) built on LayerZero, allowing it to be seamlessly bridged across different chains. StakeStone leverages LayerZero’s solutions to develop customized contracts, enhancing STONE’s cross-chain compatibility.&#x20;

By leveraging Native's liquidity infrastructure, STONE enables users to perform seamless cross-chain redemptions with optimized pricing and speed, all with a single click. Our integration with Native's PMM tackles liquidity fragmentation, resulting in lower costs, better prices, and higher capital efficiency.

### **Withdrawal Process**

StakeStone provides two methods for withdrawals: **\[Request]** and **\[Instant]**.

**Instant Withdrawal** leverages Native's PMM liquidity infrastructure to provide users with instant omnichain withdrawals. By depositing a certain amount of ETH into Native's lending pool, our buffer pool allows users to easily convert STONE back to ETH across different chains with a single click.

\*Only available when there is remaining ETH in the buffer pool&#x20;

**The Request Withdraw** method is slower because, after users initiate withdrawals, STONE must be unstaked from various restaking protocols before ETH can be returned to the user.

### **The Price of STONE**

The amount of ETH you can withdraw with STONE is based on the price of STONE in smart contracts.

The price of STONE is determined by the smart contract and is not influenced by DEX prices or information platforms like CoinGecko. This contract-based price is used for both deposits and withdrawals, ensuring users can always redeem their ETH according to the current STONE price in the contract. Users can view the STONE price for deposits and withdrawals on [StakeStone's dApp](https://app.stakestone.io/u/stake).

For more information on STONE's pricing mechanism, please visit [Pricing](/stakestone/stone-eth/how-it-works/pricing)


# \[Instant]

For the \[Instant] method, users can withdraw ETH with their STONE immediately without waiting for settlement. The advantage of \[Instant] is that users receive their ETH faster. However, this method involves an additional gas fee and higher slippage.&#x20;

When there is undeployed ETH available in the buffer pool, users can instantly withdraw ETH from the buffer pool without incurring extra gas fees or slippage.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2F4CpFHs73tsMnx9vXow65%2Fimage.png?alt=media&amp;token=734eae79-c928-48f4-8da2-a61a2e59e411" alt=""><figcaption></figcaption></figure>


# \[Request]

For the \[Request] method, users can submit the amount of ETH they wish to redeem. The requested ETH will be available to claim after the next settlement, which typically occurs a few days later depending on the total amount of ETH requested.&#x20;

The \[Request] method offers the advantage of lower gas fees and minimal to no slippage; however, users must wait for a certain period for their request to be processed.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2F3gLfTXqF3BR3bC0WhAc3%2Fimage.png?alt=media&amp;token=4a6f8ce0-259f-43c9-bf94-d33b6688f957" alt=""><figcaption></figcaption></figure>


# OPAP

The Optimizing Portfolio and Allocation Proposal (OPAP) mechanism is the first decentralized solution for management and optimization of liquid staking yields. Unlike traditional approaches that rely on MPC wallets, StakeStone provides full transparency for underlying assets and yields.

OPAP allows for the optimization of STONE’s underlying assets, ensuring that STONE holders receive optimized staking yields automatically and effortlessly. This includes:

* **Portfolio Optimization**: Adding new strategies to the underlying assets of STONE
* **Allocation Optimization**: Changing the proportion of ETH among different strategies

### How does OPAP ensure safety?&#x20;

OPAP prioritizes safety over APY when evaluating new assets. STONE holders focus on three key risks: market risk, counterparty risk, and technology risk. Specifically, market risk concerns liquidity, counterparty risk involves governance, legal issues, and centralization, while technology risk pertains to smart contracts and oracle reliability. Thus, STONE holders prefer low-risk, blue-chip assets as underlying assets.&#x20;

Past assets approved by OPAP include Symbiotic, Eigenlayer, Rocketpool, Curve, Balancer, and Mellow.

Our asset evaluations emphasize safety (third-party audits), adoption (measured by the number of staked on-chain wallets), and liquidity (to minimize slippage and large price fluctuations). To ensure safety, we consult a committee of the largest institutional STONE holders, who provide independent internal risk assessments and due diligence to verify if an asset meets our blue-chip standards.

Our developer team includes experts from reputable audit firms such as Slowmist, ensuring that all code undergoes an internal audit before being externally reviewed by institutional partners and third-party auditors.

OPAP also has a timelock mechanism in the smart contract code (minimum 24 hours). Usually, the timelock is longer, averaging 3 to 7 days while integrating community feedback for OPAP and this timelock serves as a safety guardrail.

### **How** OPAP **Works** <a href="#how-opap-works" id="how-opap-works"></a>

**WHEN TO VOTE**

Any adjustment to funds must first be proposed and displayed in the form of a proposal. The holders of STONE will determine the final decision on whether to execute the proposal through on-chain voting.

**WHO CAN VOTE**

All STONE holders can vote in favor or against the proposal in `OPAP` on StakeStone's website, with the weight determined by the number of STONE they lock.

**HOW TO DECIDE**

* The final decision on whether to pass and execute the proposal will be based on the number of votes in favor and against the proposal.
* The proposal will be implemented if it receives more affirmative votes than opposing votes at the end of the public notice period.
* When nobody vote for or against in one proposal when the voting period ends, it will NOT be implemented.

**HOW TO PROPOSE**

* Currently, proposals can be raised by this address: **`0xc52d678f99bfc43ae777a16a79b78db571a3e2a1`**
* All past and active proposals (OPAP) can be found and voted on StakeStone's website or directly [here](https://app.stakestone.io/u/portfolio-allocation/vote/vote-list). We will send reminders for each proposal and we also strongly encourage you to set up your own reminders.
* StakeStone will gradually transition to DAO governance to decentralize the proposal submission, relevant parameter adjustments, and rule decisions.

The StakeStone team strongly encourages STONE holders to actively participate in these OPAP proposals, contributing to the development of a safer and fully decentralized ecosystem.


# Pricing

The price of STONE within StakeStone is derived from smart contracts, distinct from the prices seen on decentralized exchanges. When users deposit or withdraw assets in StakeStone, these transactions are executed based on an internal price determined by the contract, rather than by fluctuating DEX prices. For instance, if a user currently holds 1 STONE, they can withdraw approximately 1.0021 ETH via StakeStone's frontend.

**How is STONE’s Price in the Contract Calculated?**

The price of STONE within StakeStone’s smart contract is determined by two key factors: the total value of underlying assets in StakeStone and the current total supply of STONE. The contract calculates the price of STONE by dividing the total value of these underlying assets by the current total supply, providing an accurate and transparent valuation that users can verify on-chain.

**Where Can I Find STONE’s Price?**

Users can check the current price of STONE by accessing our dApp at [stakestone.io](http://stakestone.io). The exchange rate displayed on the dApp is also used for calculating withdrawals, ensuring consistency and transparency.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FWYsOUe443NhIOMWF3exq%2Fprice1.png?alt=media&amp;token=ab95283c-1427-4c17-8756-69d2169bf665" alt=""><figcaption><p>Stake Function Exchange Rate Display</p></figcaption></figure>

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FGJUvoRhdZ9qEkj4jxoWY%2Fprice2.png?alt=media&amp;token=5f70d6a2-8117-461b-907a-dde39a0b2434" alt=""><figcaption><p>Unstake Function Exchange Rate Display</p></figcaption></figure>

**Why Are STONE Prices on DEXs and Information Platforms Different from StakeStone’s dApp?**

The price of STONE on DEXs is influenced by the composition and depth of its liquidity pool. When liquidity is insufficient on a DEX, the price of STONE may become inaccurate, leading to a high price impact during swaps. Information platforms typically pull prices from these DEX sources, which may not reflect the true value of STONE as calculated by StakeStone’s smart contract.

This discrepancy between the contract price and the DEX price creates arbitrage opportunities. For example, if the contract price of STONE is 1.1 ETH, and a user purchases 1 STONE for 0.8 ETH on a DEX, they can then exchange that 1 STONE for 1.1 ETH on StakeStone, capitalizing on the difference.

To mitigate these discrepancies and stabilize the DEX price, additional liquidity will soon be added on Manta Pacific, which will help align DEX prices more closely with those displayed on StakeStone’s dApp.


# Bridging

Built on LayerZero and enhanced with StakeStone's customized contracts, STONE has the following cross-chain features:

1. **Cross-Chain Asset Transfer:** STONE is an Omnichain Fungible Token (OFT) with bridging capabilities supported by LayerZero. StakeStone has developed custom contracts to facilitate the bridging of STONE across different chains without burning it on the source chain.

   Instead, STONE is locked in the contract of the source chain and can only be released when it is bridged back via LayerZero. This mechanism ensures the stability of STONE's price within the contract.
2. **Cross-Chain Price Feed:** The price of STONE is determined by the total quantity of underlying assets and its circulating supply.

   Anyone can use LayerZero to relay this price information to the target chain at any time. Developers can then directly access and utilize this price within the STONE token contract, ensuring accurate and transparent pricing across chains.
3. **Bridging:** Users can bridge STONE to and from the currently supported chains via StakeStone's website.

   It is important to note that bridging from Manta Pacific to Ethereum Mainnet is currently disabled until the conclusion of Manta's New Paradigm initiative.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FahF9S6I3Okqfc6BLL7h7%2Fbridge1.png?alt=media&amp;token=c079ce2d-2214-4968-bc9d-f7687c5c1032" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FYpV0qaXtzcCf864gwdHF%2Fbridge2.png?alt=media&amp;token=c4f3f1da-aae8-4e7d-9e18-e08cb5bd7036" alt=""><figcaption></figcaption></figure>

For STONE BTC, bridging will be available alongside Bitcoin L2’s launch of mainnet.


# Background

Bitcoin serves as an if not the most important cornerstone of crypto, yet native BTC from the Bitcoin chain lacks smart contract functionality, limiting its liquidity and integration with DeFi protocols.&#x20;

The lack of robust liquidity is the primary obstacle preventing BTC assets from realizing their full potential within EVM chains and other ecosystems. This limitation effectively freezes a vast reservoir of dormant liquidity within the BTC ecosystem, restricting its value to flow to other ecosystems and preventing it from playing a more active role in the broader DeFi landscape.&#x20;

At StakeStone, we believe a strong BTC asset in the EVM ecosystems should have the following key features, and have built SBTC and STONEBTC with the following features in mind:&#x20;

1. Liquidity&#x20;
2. Use cases&#x20;

STONEBTC and SBTC together represent a comprehensive solution for enhancing the liquidity, utility, and yield potential of BTC assets within the EVM ecosystems and other chains. By addressing this liquidity challenge, StakeStone's BTC assets aim to significantly expand BTC assets' use cases in the crypto ecosystem, providing our users with liquidity and yield.&#x20;

StakeStone's innovative BTC assets empower users to fully unlock the potential of their BTC holdings, providing unmatched liquidity and efficiency in the ever-evolving world of crypto.


# SBTC

#### **Introducing SBTC ("StakeStoneBTC")**

SBTC is designed to act as a liquid, index BTC, addressing the issue of illiquid native BTC assets by providing robust omnichain liquidity. This innovative solution will facilitate BTC asset trading and enhance the utility of native BTC within EVM ecosystems as well as other Layer 1 and Layer 2 networks. SBTC will be composed of a diversified basket of ERC20 tokens, primarily BTCB, ensuring a solid foundation of liquidity.

**Key Features of SBTC**

* **Manifold use cases**: Through close collaboration with leading ecosystems and blue-chip DeFi protocols, SBTC will have a wide range of outstanding use cases, such as various DeFi protocols on Berachain. These use cases will generate more yields for SBTC and unlock the potential of more BTC assets.
* **Omnichain Liquidity**: SBTC is designed to offer seamless liquidity across multiple chains, solving the liquidity fragmentation problem inherent in existing BTC derivatives. Upon launch, SBTC will enjoy immediate omnichain liquidity, facilitated by Native's PMM mechanism, which ensures optimal pricing and liquidity depth.
* **Instant Withdrawals**: Users can benefit from instant withdrawals with a 1:1 BTC ratio. This feature leverages BTCB's liquidity, ensuring that SBTC holders can easily convert their assets into native BTC.

**Architecture of SBTC**

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FyfDMh6UHGxj8c9kspuYV%2FIMAGE%202024-10-10%2022%3A13%3A22.jpg?alt=media&amp;token=e86df084-f8fe-45e6-bfcf-f4458ab54bc9" alt=""><figcaption></figcaption></figure>


# STONEBTC

### **Introducing STONEBTC**

STONEBTC is a yield-bearing BTC derivative designed to unlock the full earning potential of Bitcoin holdings while maintaining seamless liquidity across DeFi ecosystems. By integrating advanced BTC yield strategies across **DeFi, CeDeFi, and RWA**, STONEBTC allows users to earn sustainable yields without sacrificing flexibility or utility.&#x20;

### **Key Features of STONEBTC**

* **Automatically Optimized Yields**: STONEBTC provides users with access to advanced, automatically optimized yield strategies, similar to StakeStone’s ETH-based product, STONE. By leveraging diverse yield sources, including Bitcoin staking and restaking networks like Babylon and Symbiotic, STONEBTC dynamically allocates assets to maximize returns and generate sustainable yields without the need for active management, creating a seamless, hands-off experience.
* **Omnichain Liquidity**: STONEBTC provides users with omnichain liquidity, thus ensuring liquidity for time-locked BTC assets and providing more flexible methods for exit liquidity.
* **Enhanced Capital Efficiency**: By allowing users to earn yields while retaining the ability to utilize their assets in DeFi, STONEBTC enhances capital efficiency. Users can participate in a wide range of DeFi activities, including DEX trading, lending platforms, CDP collateralization, derivatives trading, and even GameFi.&#x20;

### How Does STONEBTC Work?

Getting started with STONEBTC is straightforward:

• Deposit your SBTC or LBTC into StakeStone’s protocol.

• Your holdings are automatically converted into STONEBTC.

• From the moment of deposit, STONEBTC begins generating yield through StakeStone’s underlying strategy vaults.

StakeStone’s vaults are designed to integrate multiple yield sources, combining the innovation of DeFi protocols, the stability of CeDeFi institutions, and the growth potential of RWA projects. This balanced approach ensures sustainable and optimized returns for BTC holders.

As StakeStone expands support for additional BTC derivatives, STONEBTC will continue to evolve, further enhancing its versatility and accessibility.

#### Withdrawals&#x20;

Users can request a withdrawal of their STONEBTC holdings at any time. StakeStone, in collaboration with our market maker, ensures that withdrawals are processed and completed immediately to seven days. This process is designed to guarantee maximum security for users’ assets while maintaining efficient liquidity management.

### Conclusion

STONEBTC is not just another BTC derivative. Combined with SBTC (”StakeStoneBTC”), StakeStone’s BTC products are designed to solve two key problems BTC holders face: low or inconsistent yields and restricted liquidity.

In the future, we plan to integrate STONEBTC into even more use-case scenarios, including **payment solutions** and other innovative financial utilities. As the omnichain DeFi landscape grows, so too will the opportunities for STONEBTC!


# STONE Pools

StakeStone's Omnichain Liquidity Marketplace

STONE-Fi is an omnichain liquidity distribution marketplace designed specifically for the application layer, facilitating seamless redistribution of liquidity across ecosystems and protocols. By bridging the gaps between native liquidity and various ecosystems, and aligning incentives among liquidity providers, protocols, and ecosystems, StakeStone ensures that liquidity is efficiently allocated where it’s needed most.

**Earning with STONE-Fi Pools**

After staking ETH and receiving STONE, users can further enhance their returns by providing liquidity in one of our STONE-Fi pools. Leveraging the omnichain capabilities of STONE-Fi, users can seamlessly move liquid assets across chains, deposit into various LP mining pools, and unlock the full potential of their STONE holdings.&#x20;

STONE-Fi offers a diverse range of mining pools across multiple chains and protocols, allowing users to earn LP rewards with STONE trading pairs on DEXs, market-making protocols, lending platforms, CDPs (Stablecoin), derivatives, and GameFi. Each LP route within STONE-Fi is accompanied by detailed information explaining how rewards are earned and calculated.

The STONE-Fi dashboard allows users to track their liquidity provision, rewards, and APY, providing a comprehensive view of their earnings and opportunities.

**Decentralization & Ecosystem Sustainability**&#x20;

STONE-Fi serves as a powerful tool within StakeStone's ecosystem, ensuring that liquidity is effectively allocated to prime opportunities and that participants are incentivized to contribute to the platform's long-term success.


# LiquidityPad

StakeStone's Omnichain Liquidity Issuance Platform

### Introduction

The blockchain landscape is rapidly evolving, entering **an era of diversification and specialization** where each blockchain functions as **a unique digital economy with distinct liquidity demands**, specializing and catering to specific use case scenarios. While Ethereum stands as a liquidity powerhouse abundant with assets, emerging ecosystems face significant hurdles in acquiring and deploying efficient, organic, and sustainable liquidity to fuel their growth.

StakeStone LiquidityPad is an **innovative omnichain liquidity issuance platform**, strategically designed to bridge Ethereum’s liquidity-rich environment with the evolving demands of emerging chains.&#x20;

By offering a **tailored and structured liquidity fundraising solution**, LiquidityPad empowers projects to secure liquidity that is tailored and aligned with their unique ecosystems while providing users with yield opportunities across the omnichain landscape.&#x20;

### Addressing The Liquidity Challenge

Emerging blockchains face potential hurdles in acquiring and retaining efficient liquidity. While Ethereum offers a vast pool of liquidity, cross-chain friction, opportunity costs, and fragmented infrastructures hinder efficient liquidity flow.&#x20;

Without **an efficient bridge to Ethereum’s robust liquidity**, emerging ecosystems face potential barriers that hinder their growth potential. StakeStone’s LiquidityPad eliminates these inefficiencies, enabling projects to acquire liquidity efficiently through StakeStone's omnichain infrastructure.

**Key challenges include:**

* **Capital Opportunity Cost:** Projects must incentivize asset migration from Ethereum, competing with native staking yields and DeFi opportunities
* **Cross-Chain Complexity:** Traditional methods expose users to bridge risks, high transaction costs, and fragmented liquidity pools
* **Lack of Efficient Distribution:** Without tailored solutions, liquidity often becomes stagnant, failing to support protocol growth dynamically

StakeStone’s LiquidityPad addresses these issues by offering a customized and tailored omnichain liquidity issuance platform that allows projects of all stages to attract, manage, and retain liquidity sustainably.

### LiquidityPad: An essential Omnichain Pipeline&#x20;

Through a **structured omnichain liquidity distribution model**, LiquidityPad serves as an essential pipeline, ensuring **bilateral** **capital flows across ecosystems** by enabling Ethereum-based assets to be seamlessly deployed across emerging chains while empowering ecosystem assets to access Ethereum’s mature DeFi infrastructure for further value creation.

**Highlights**

1. **Tailored Liquidity Issuance:** Projects can launch tailored pre-deposit liquidity vaults aligned with their growth strategies and ecosystem-specific demands&#x20;
2. **Omnichain Liquidity Access:** Seamlessly channel liquidity between Ethereum and emerging chains, unlocking new DeFi and yield opportunities
3. **Capital Efficiency:** Users can maximize yield opportunities while maintaining access to liquid assets
4. **Security & Transparency:** Fully on-chain, non-custodial infrastructure ensures complete asset visibility and security

### Benefits for LPs&#x20;

Liquidity providers play a crucial role in driving the LiquidityPad ecosystem, benefiting from early-stage incentives and yield opportunities to maximize their capital efficiency. Through active participation, users can:

* **Earn Early-Stage Rewards:** Gain access to project-specific airdrop rewards and incentives
* **Amplify Yield Opportunities:** Utilize LP tokens within Ethereum’s blue-chip DeFi ecosystem for additional yield generation
* **Seamlessly Navigate Ecosystems:** Enjoy frictionless access to emerging blockchain projects without exposure to unnecessary risks

By acting as a strategic gateway, LiquidityPad allows users to engage in high-yield opportunities with confidence while supporting the growth of emerging ecosystems.

### Conclusion

As blockchain ecosystems continue to diversify, the need for **efficient, omnichain liquidity distribution solutions** has never been greater. StakeStone’s LiquidityPad establishes itself as **the critical omnichain liquidity infrastructure** connecting Ethereum’s liquidity-rich environment with emerging chains that require efficient capital, driving sustainable growth across ecosystems while maintaining robust security, capital efficiency, and optimized yield for users.&#x20;


# How LiquidityPad Works

Upon depositing assets, users receive **LP tokens**, which represent their share in the liquidity vault. These LP tokens can be leveraged across Ethereum’s DeFi ecosystem, unlocking multiple opportunities:

* **Liquidity Provision and Trading on DEXs:** Users can deploy LP tokens on DEXs such as **Uniswap and Curve**, providing liquidity to earn trading fees or trade LP tokens directly
* **Collateralized Borrowing:** LP tokens can be used as collateral on lending platforms such as **Aave and Morpho**
* **Yield Optimization Strategies:** Through platforms like **Pendle**, users can trade or lock in their future yields, optimizing their returns based on market conditions
* **Ecosystem Incentives:** LP tokens provide access to exclusive opportunities such as **airdrops, governance rights, and reward programs** from partner protocols

LiquidityPad's flexible and customizable liquidity infrastructure enables users to enhance their returns while providing emerging ecosystems with a long-term, tailored liquidity solution.


# Supported Assets

To provide **maximum adaptability and accessibility**, LiquidityPad supports a broad range of assets, including but not limited to:

* **Ethereum-based assets:** ETH, WETH
* **Bitcoin derivatives:** WBTC, cbBTC, BTCB, LBTC, FBTC
* **Stablecoins:** USDT, USDC
* **StakeStone’s native assets:** [**STONE**](/stakestone/stone-eth/background)**,** [**SBTC**](/stakestone/sbtc-and-stonebtc/sbtc)**, and** [**STONEBTC**](/stakestone/sbtc-and-stonebtc/stonebtc)


# BTC Pools


# Gauge

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FCMyxQgy8SQLaO8RbDWSh%2Ftokenomics.png?alt=media&amp;token=7fca0342-8216-428d-bcca-c0a42dc6cd15" alt=""><figcaption></figcaption></figure>

Gauge Weight is determined by voting power in total, i.e. how much STO and how long STO has been locked up.&#x20;

veSTO holders can participate in gauge voting to determine STO emissions. Users can allocate their vote (1 veSTO = 1 vote) to one or more gauges (a gauge corresponds to an LP token of a pool) through the StakeStone dapp.&#x20;

Every bi-weekly, STO emission distribution voting is done in Gauge.&#x20;

STO emission to a gauge is proportional to the votes it receives.


# Emissions Allocation

How STO is distributed among various liquidity pools

STO is the governance token of the StakeStone Protocol, serving as a crucial component in decentralized governance and sustainability of the ecosystem. When users lock their STO tokens, they receive veSTO tokens in exchange, which grant them voting power within the STONE-Fi ecosystem. This voting power enables users to participate in key decisions, such as determining how rewards are distributed among different liquidity pools, protocol upgrades, etc.

**Earning veSTO Rewards**

Locking STO tokens allows users to earn veSTO rewards, which are proportional to the amount of STO locked and the duration of the lockup period. The longer and larger the lock, the greater the rewards users can earn.&#x20;

This system encourages long-term commitment to the protocol, rewarding those who contribute significantly to its stability and growth.

#### Voting & Governance&#x20;

veSTO holders play a pivotal role in the governance of the STONE-fi ecosystem. Through gauge voting, veSTO holders can direct emissions toward specific pools or activities they support, thereby influencing the distribution of incentives across the platform. Every bi-weekly, STO emission distribution voting takes place in the Gauge. The amount of STO emissions allocated to each gauge is directly proportional to the number of votes it receives. This voting mechanism empowers veSTO holders to shape the strategic focus of the protocol, ensuring that emissions are allocated in alignment with the community’s priorities.

**Emissions Allocation Process**

The allocation of emissions is determined through gauge voting by veSTO holders. For instance, the community might vote to allocate more emissions to a liquidity pool that supports a crucial trading pair or a new strategic partnership. This decentralized approach ensures that emissions are utilized effectively to promote the protocol's growth and sustainability, aligning incentives between key players within the STONE-fi ecosystem.

#### Conclusion&#x20;

By allowing the community to control emissions allocation, StakeStone ensure that incentives are aligned with the most valuable and active participants in the ecosystem. Also encouraging users to participate actively in governance and liquidity provision, ensuring that the protocol remains decentralized and community-driven.&#x20;

In the long term, by using community votes to determine emissions allocation helps balance the supply of new tokens with demand, community controlled emissions allocation help manage token inflation and maintain the protocol’s long-term sustainability.


# STO

STO is the governance token that powers StakeStone's omnichain liquidity infrastructure. It serves as the cornerstone of the protocol's governance while creating sustainable value for all participants in the StakeStone ecosystem.

Through a carefully designed vote-escrowed token model (veSTO), STO aligns incentives between liquidity providers, governance participants, and protocols within the StakeStone ecosystem. The token provides utility across multiple dimensions while employing innovative mechanisms to continuously capture value and ensure long-term protocol sustainability.&#x20;

#### Quick Navigation:

1. **Converting between STO and veSTO**&#x20;

{% content-ref url="/pages/4uZFsw0eWAObYeGu1qs5" %}
[Conversion](/stakestone/governance/sto/conversion)
{% endcontent-ref %}

2. **How to lock veSTO to unlock voting power**&#x20;

{% content-ref url="/pages/g3s7XMflmogNg9i4OF8T" %}
[Lock](/stakestone/governance/sto/lock)
{% endcontent-ref %}

3. **Participating in StakeStone's governance**&#x20;

{% content-ref url="/pages/m3NGN9Ibq8tady92i7cv" %}
[Vote](/stakestone/governance/sto/vote)
{% endcontent-ref %}

4. **Utilizing the Treasury asset swap mechanism**&#x20;

{% content-ref url="/pages/5AmN3djRvMCQeoNpvcHT" %}
[Swap & Burn](/stakestone/governance/sto/swap-and-burn)
{% endcontent-ref %}

## Token Utility

STO enables multiple forms of utility within the StakeStone ecosystem. By locking veSTO tokens, holders gain voting rights proportional to their locked tokens as well as other benefits, including boosted yield and bribe rewards.&#x20;

#### Governance&#x20;

* **Emission Allocation**: veSTO holders vote on the allocation of veSTO emissions across STONE-Fi pools, BTC-Fi pools, and LiquidityPad vaults.
* **Protocol Parameter Control**: veSTO holders influence key protocol parameters, including the amount of platform fees charged and percentage of bribes burned.
* **Strategic Direction**: Governance participants help shape StakeStone's development roadmap and strategic initiatives.

#### Liquidity Incentives & Rewards

* **Yield Boosting**: Liquidity providers who lock veSTO receive boosted yields on their provided liquidity. For each amount of liquidity deposited, a proportional quantity of veSTO must be locked to maximize yield boosts. If insufficient veSTO is locked, the yield boost applies only to a portion of the deposited liquidity.
* **Bribe Rewards**: veSTO voters earn a portion of bribes from the STONE-Fi pools, BTC-Fi pools, and LiquidityPad vaults they voted for.
* **veSTO Emissions**: When veSTO holders vote on specific pools or vaults for emission allocation, they also secure a proportional claim to the associated veSTO rewards.
* **Treasury Asset Access**: STO represents proportional rights to assets in the StakeStone Treasury through the [Swap & Burn](/stakestone/governance/sto/swap-and-burn) mechanism.

## Value Capture Mechanism

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FwKoT2w39zxqJnqNTLOgg%2FValue%20Capture%20Mechanism.png?alt=media&amp;token=caee4042-2d3d-43c0-acac-5b58bad2c6cb" alt=""><figcaption><p>STO Value Capture Mechanism</p></figcaption></figure>

StakeStone integrates a network of interconnected mechanisms designed to drive sustainable growth for both the protocol and its treasury while ensuring consistent value accrual for STO holders. The Treasury is powered by two revenue streams, complemented by an innovative [Swap & Burn](/stakestone/governance/sto/swap-and-burn) mechanism that reinforces long-term value sustainability.

#### 1. Platform Fees

Platform fees, such as exit fees from STONE vaults, SBTC & STONEBTC vaults, and LiquidityPad, will be directed to the Treasury. These fees consist of blue-chip assets such as ETH, Bitcoin, and stablecoins.&#x20;

#### 2. Bribe Mechanism&#x20;

Our bribe mechanism creates mutual benefits for protocols seeking liquidity and governance participants. Ecosystem builders and protocols can purchase STO tokens to deposit as bribes into STONE-Fi pools, BTC-Fi pools, or LiquidityPad vaults, creating targeted incentives that attract liquidity where it's most needed.

When STO serves as the bribe currency, a portion is immediately burned upon deposit, generating continuous deflationary pressure that benefits all token holders. A remaining portion flows directly to veSTO holders who directed their votes toward the respective pools, creating a direct economic incentive for active governance participation.

Beyond STO-denominated bribes, the Treasury will take partner ecosystem governance tokens as bribes. This not only provides highly targeted incentives for specific pools but also expands the Treasury's asset diversity. For governance participants, these varied token streams create additional value capture opportunities.&#x20;

Our multi-token Treasury approach strengthens cross-ecosystem relationships, allowing for diversified rewards to our ecosystem.&#x20;

## Conclusion: Building Sustainable Governance&#x20;

StakeStone's governance and tokenomics model is designed to ensure incentive alignment across all stakeholders—from liquidity providers to ecosystem builders and everyday users. At the heart of StakeStone's governance lies the vote-escrowed token model, creating a framework that balances accessibility with long-term commitment. The multi-layered incentive structure rewards meaningful participation, while the deflationary mechanisms provide sustainable value accrual.&#x20;

As the protocol grows, STO will continue to expand in utility through the very governance mechanisms it enables, allowing the StakeStone community to collectively shape the future of StakeStone's omnichain liquidity infrastructure.


# Conversion

StakeStone's governance system is built on a vote-escrowed token model that encourages long-term alignment with the protocol. This page explains the processes for converting between STO and veSTO.

### STO to veSTO Conversion&#x20;

#### Process

1. Navigate to the "DAO" section of the StakeStone dApp and select the "STO <=> veSTO" tab;
2. Enter the amount of STO to be converted to veSTO. Each STO token converts to exactly one veSTO token. The conversion takes effect immediately, with no delay or vesting period;
3. Users' veSTO balance will update immediately after the transaction is confirmed.&#x20;

### veSTO to STO conversion&#x20;

The process of converting veSTO back to STO incorporates a carefully designed vesting period that ensures protocol stability and protects against potential governance attacks. This balanced approach allows participants to exit their governance position while maintaining the integrity of the StakeStone ecosystem.

#### Process

1. Navigate to the "DAO" section of the StakeStone dApp and select the "STO <=> veSTO" tab;
2. The conversion maintains a 1:1 ratio throughout the process—each veSTO token will become exactly one STO token once the vesting concludes;
3. The amount of veSTO deposited for conversion enters a 30-day vesting period. During this vesting period, the veSTO is effectively locked—meaning it cannot be used for re-locking, voting, or receiving yield boost benefits;
4. During the 30-day vesting, user can check total claimable STO, different claim orders and the corresponding amount of veSTO in vesting, as well as estimated claimable time for each independent claim;
5. Once the 30-day vesting period concludes, users can claim their STO tokens.

The 30-day vesting period begins at the exact moment users initiate the conversion. This process cannot be cancelled once initiated. If a user has multiple conversion transactions in progress (perhaps initiated at different times), the user will need to claim each one individually as they reach their vesting completion.


# Lock

The StakeStone governance system uses a vote-locking mechanism that allows veSTO holders to lock their tokens to gain voting power and additional benefits. This page explains how locking veSTO works, its benefits, and the process for participating in this core governance function.

### Understanding veSTO Locking&#x20;

After converting STO to veSTO, users must lock their veSTO to activate its voting capabilities and additional benefits. The locking mechanism serves several important purposes:

1. **Ensuring Commitment**: Requiring users to lock veSTO demonstrates commitment to the protocol's long-term health.
2. **Preventing Governance Attacks**: The locking period prevents short-term manipulation of governance decisions.
3. **Aligning Incentives**: By locking veSTO, StakeStone protocol rewards users who demonstrate greater commitment to the protocol.

### Benefits of Locking veSTO&#x20;

1. **Governance Power**: By locking veSTO, users can influence veSTO emissions as well as make community-driven decisions about platform fees and percentages of bribes burned.&#x20;
2. **Yield Boost**: Locking veSTO grants holders instant access to yield boost benefits proportional to the amount of veSTO converted. A specific amount of veSTO can only boost a proportional amount of liquidity provided; if users' provided liquidity exceeds the proportional amount covered by their locked veSTO, the excess liquidity will not receive boosted yields. To maximize yield across all liquidity positions, users will need to lock sufficient veSTO.&#x20;

### Process&#x20;

Users can lock their veSTO tokens by navigating to the DAO section of the StakeStone dApp and selecting the Lock tab, where users are able to see the voting power the locked veSTO represents. Unlocking veSTO does not require a vesting period and can be unlocked immediately.&#x20;


# Vote

Voting rights are proportional to the amount of veSTO tokens locked.&#x20;

### Types of Governance Votes&#x20;

**Incentive Distribution Votes (Gauge Voting)**

By participating in gauge voting, veSTO holders can vote for specific STONE-Fi and BTC-Fi pools as well as LiquidityPad Vaults, thereby directing veSTO emissions towards these pools. By participating in gauge voting, holders are entitled to a portion of bribes and veSTO emissions proportional to their votes for the selected pool or vault.

**Protocol Parameter Votes**

Holders of locked veSTO can collectively decide and modify key protocol parameters such as fee structures, proportion of bribes burned, and other protocol initiatives.&#x20;

### Benefits of Gauge Voting

1. **veSTO Emissions**: When veSTO holders vote on specific pools or vaults for emission allocation, they also secure a proportional claim to the associated veSTO rewards.
2. **Bribe Rewards**: When protocols and ecosystem builders bribe specific pools or vaults, a proportion of bribes are distributed as rewards proportionally to the amount of veSTO voted.


# Swap & Burn

The innovative Swap & Burn mechanism is designed to create sustainable value and diversified returns for STO holders while maintaining deflationary pressure on the token supply. This page explains how the mechanism works and its benefits.

### Understanding Swap & Burn

The StakeStone Treasury accumulates a diversified portfolio of assets through its revenue streams:

1. **Platform Fees**: Generated from withdrawals across STONE vaults, SBTC & STONEBTC vaults, and LiquidityPad vaults
2. **Bribe Portions**: A percentage of bribes offered by protocols to attract liquidity

These assets primarily consist of blue-chip cryptocurrencies such as ETH, BTC, stablecoins, STO, and partner ecosystem governance tokens. As the protocol grows and more protocols leverage StakeStone's liquidity solutions, the Treasury naturally expands in asset diversification, creating increasing value that backs the STO token.

The Swap & Burn mechanism allows STO holders to exchange their tokens for a proportional share of these alternative treasury assets, effectively removing STO from circulation in the process.&#x20;

### How Swap & Burn Works

The Swap & Burn mechanism creates a powerful market dynamic by enabling arbitrage opportunities. When a user holds STO tokens, they inherently possess rights to a proportional share of the treasury's alternative assets. When the value of Treasury assets corresponding to a specific amount of STO exceeds STO's market value, users can:

1. Acquire STO tokens on the open market
2. Swap these tokens for their proportional treasury assets
3. Realize the value difference as profit

This process simultaneously:

* Removes STO from circulation through permanent burning
* Distributes alternative blue-chip assets to STO holders&#x20;
* Creates natural price discovery and a soft value floor for STO

The arbitrage potential incentivizes market participants to constantly monitor and maintain efficient pricing, creating a self-regulating, organic, and sustainable ecosystem that protects STO value.

### Benefits of Swap & Burn Mechanism&#x20;

* **Flexible Exit Options**: Enables direct exchange for blue-chip treasury assets without relying on exchange liquidity
* **Portfolio Diversification**: One swap provides exposure to multiple blue-chip assets in the treasury
* **Market-Driven Deflation**: Creates natural token burns triggered by arbitrage opportunities
* **Value Accrual for Holders**: As tokens are burned, each remaining STO represents a larger claim on treasury assets


# Roadmap

StakeStone has achieved significant milestones since its inception and continues to build towards an ambitious future. Our journey maps our evolution from a testnet launch to becoming a comprehensive omnichain liquidity infrastructure with expanding use cases.

## 2023: Foundation Building&#x20;

#### Q3 2023

* **July**: Testnet launched, marking StakeStone's official entry into the DeFi space
* **September**: Mainnet launched with initial 1.1k ETH TVL reached

#### Q4 2023

* **December**: Established liquidity partnership with Manta New Paradigm
* **Key Metrics**:
  * **TVL**: 290k ETH (\~$645 Million), becoming the 5th largest stETH holder on-chain
  * **Users**: 93,560 users onboarded
  * **Ecosystem**: Successfully integrated with 10+ protocols

## 2024: Expansion & Strategic Growth

#### Q1 2024

* **February**: Partnered with BTC ecosystem to bootstrap liquidity
  * **TVL**: 310k+ ETH (\~$870 Million)
  * **Users**: 96,000 users
* **March**: Secured Strategic Round investment from Binance Labs and OKX Venture

#### Q2 2024

* **May**: Successfully bootstrapped Scroll's liquidity, contributing to its DeFi ecosystem growth
* **June**:
  * Integrated restaking solutions with Eigenlayer and Symbiotic
  * Established strategic partnerships with emerging ecosystems:
    * Berachain
    * Linea
    * Monad
    * Plume
  * Engaged with blue-chip DeFi protocols including Aave and Morpho

#### Q3 2024&#x20;

* **August**: Integrated with Native intent-based liquidity infrastructure, leveraging PMM lending pools to establish deep and efficient omnichain liquidity
* **September**:
  * Hosted Liquid Asset Summit in collaboration with Berachain and Hashkey Cloud during Token2049 Singapore

#### Q4 2024

* **November**:
  * Launched SBTC and STONEBTC products, revolutionizing BTC liquidity
  * Closed Series A funding round led by Polychain Capital
* **December**:
  * Launched one of the leading pre-deposit DeFi vaults on Berachain, strategically targeting retail users
  * Established partnership with Lido and P2P.org

## 2025: Product Diversification & Ecosystem Expansion

#### Q1 2025

* Launched LiquidityPad to redefine the future of omnichain liquidity, allowing users to unlock alpha and earn token rewards by contributing liquidity to a wide range of cross-chain applications and ecosystems

#### Q2 2025

* Partnering with Monad & WLFI to provide StakeStone's omnichain liquidity solution, establishing a strategic collaboration with a trailblazer in the blockchain ecosystem
* Launch of StakeStone Governance DAO powered by Vote-Escrowed Token (veToken) model, with functions such as conversion, locking, voting and Swap\&Burn
* Develop innovative crypto payments product for individual economies powered by AI

#### Q3 2025&#x20;

* Restructuring of STONEBTC product with CeDeFi and RWA integrations to better support sustainable and optimized yields&#x20;
* Full-scale launch of payment app ("Pebbles") with comprehensive features:
  * Fully support EIP-7702
  * Smart Savings that produce consistent yields&#x20;
  * AI-driven financial analytics tailored to individual economies

#### Q4 2025

* Expand omnichain liquidity services to a wider range of RWA and high-performance chains
* Develop advanced AI-driven financial solutions tailored for users of individual economies for our payment app to deliver an unprecedented smart account experience


# Tokenomics

STO is the native utility and governance token of the StakeStone ecosystem, designed to align long-term incentives across all stakeholders, including users, partners, and builders. The token supports key functionalities such as protocol governance, yield boosting, and access to bribe rewards through vote-escrowed STO (veSTO).

### Allocation&#x20;

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FC4D0WtldRYJpQywA5KfR%2FGnlr_JNaMAIFbdw.jpeg?alt=media&amp;token=72eaf0c5-0c23-4431-89c3-f2031a462c30" alt=""><figcaption><p>STO Distribution</p></figcaption></figure>

**Total Supply**: 1,000,000,000&#x20;

### Vesting&#x20;

StakeStone’s token distribution is designed to foster long-term alignment across contributors, investors, ecosystem participants, and community stakeholders. Each category follows a tailored vesting schedule to support sustainable protocol development and strategic growth.

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FwefjWZ0Vax61px20izkK%2FGnlsEM1aUAAUaCd.jpeg?alt=media&amp;token=803c1313-fa69-4097-889a-c056c8e25209" alt=""><figcaption><p>STO Vesting Schedule</p></figcaption></figure>


# Smart Contracts Address\_STONEUSD

<table><thead><tr><th width="271">Contract Name</th><th>Address</th></tr></thead><tbody><tr><td>STONEUSD（Ethereum）</td><td>0x6A6E3a4396993A4eC98a6f4A654Cc0819538721e</td></tr><tr><td>STONEUSD (BNB Chain)</td><td>0x8B4E28607bdcacBf937f81F29E3DAFe7Bc1D7c0b</td></tr><tr><td>STONEUSD (Monad)</td><td>0x095957CEB9f317ac1328f0aB3123622401766D71</td></tr></tbody></table>


# Smart Contracts Address\_STONE

This page shows all smart contracts address deployed on Mainnet and Testnet.

## For Mainnet

<table><thead><tr><th width="258.5">Contract Name</th><th>Address</th></tr></thead><tbody><tr><td>Minter</td><td>0xEc306E46549A7E8f4fCE823D3058f2D134133B17</td></tr><tr><td>Stone(Ethereum)</td><td>0x7122985656e38BDC0302Db86685bb972b145bD3C</td></tr><tr><td>Stone(BNB)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>STONE (Berachain)</td><td>0xEc901DA9c68E90798BbBb74c11406A32A70652C3</td></tr><tr><td>Stone(Scroll)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>Stone(Manta)</td><td>0xEc901DA9c68E90798BbBb74c11406A32A70652C3</td></tr><tr><td>STONE(Aptos)</td><td>0x543c5660aa4d496687e2068c11765f04607c4f4b639a83233a9333604fb8ce59</td></tr><tr><td>Stone(Mode)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>STONE(Zircuit)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>Stone(Astar zkEVM)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>STONEOFT(For Aptos)</td><td>0x8235139902590521BA96b9c26009D34080388d67</td></tr><tr><td>Stone(Linea)</td><td>0x93F4d0ab6a8B4271f4a28Db399b5E30612D21116</td></tr><tr><td>Stone(Mantle)</td><td>0x2Fde62942759d7C0aaf25952Da4098423bC1264C</td></tr><tr><td>Stone(Base)</td><td>0xD2012fc1B913cE50732ebcaa7E601fe37Ac728C6</td></tr><tr><td>Stone(Metis)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>Stone(Optimism)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>Stone(Arbitrium)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>Stone(Meter.io)</td><td>0x0978C36BCAa1887AD0335E76e184290bAA6731D0</td></tr><tr><td>Stone(X Layer)</td><td>0x80137510979822322193fc997d400d5a6c747bf7</td></tr><tr><td>Stone(SEI)</td><td>0x80137510979822322193fc997d400d5a6c747bf7</td></tr><tr><td>M-STONE(Merlin)</td><td>0xB5d8b1e73c79483d7750C5b8DF8db45A0d24e2cf</td></tr><tr><td>BStone(B2)</td><td>0x7537C1F80c9E157ED7AFD93a494be3e1f04f1462</td></tr><tr><td>StoneVault</td><td>0xA62F9C5af106FeEE069F38dE51098D9d81B90572</td></tr><tr><td>Proposal</td><td>0x3aa0670E24Cb122e1d5307Ed74b0c44d619aFF9b</td></tr><tr><td>StrategyController</td><td>0x396aBF9fF46E21694F4eF01ca77C6d7893A017B2</td></tr><tr><td>AssetVault</td><td>0x9485711f11B17f73f2CCc8561bcae05BDc7E9ad9</td></tr><tr><td>MiningPool</td><td>0x8f5420e76eEC29027800D4e3e8E879617bdE709b</td></tr><tr><td>G-NFT</td><td>0x129e49c0399E3C932D34c3b76A598214b5B82cf9</td></tr></tbody></table>

## For Testnet(Sepolia)

| Contract Name            | Address                                    |
| ------------------------ | ------------------------------------------ |
| Minter                   | 0x448bd15d7b0a532a1b0f11a535eb6dd94640679c |
| Stone(Sepolia)           | 0x0D26Efb8bb3122DEd52e814b4B428133Efc82272 |
| Stone(Berachain Testnet) | 0xA4700DFb69C5D717Cd08e5dcCa4d319F07c049Af |
| StoneVault               | 0xfbbe4d65bd61b778161ed71ec9416988ee21e911 |
| Proposal                 | 0x724a7582d85fcabd140d749bceb6efaafa018be7 |
| StrategyController       | 0xfC119BE82d07382074C14f277498bCB2176e5Ea6 |
| AssetVault               | 0x940afc1c7b792f7afed70beb7fc40bc2d09bf916 |

## For Testnet(Goerli)

| Contract Name            | Address                                    |
| ------------------------ | ------------------------------------------ |
| Minter                   | 0x436caf315d02b721907df785bc9573ca9c8a0da8 |
| Stone(Goerli)            | 0x941aC2aC418e0e6381585f8DdE74D068213BEf24 |
| Stone(Arbitrum Goerli)   | 0x4AE9067a2A01e9610dfAacaF6887BB6B2FE5d177 |
| Stone(BNB Chain Testnet) | 0xE31861dbB1608066Edea809a2E3c2a078ae1c9Bc |
| Stone(Linea Goerli)      | 0x920800a3a0d690d027FC97C09F8C36216481C4a2 |
| Stone(Base Goerli)       | 0x5d417e7798208E9285b5157498bBF23A23E421E7 |
| Stone(MANTA Testnet)     | 0x1da4dF975FE40dde074cBF19783928Da7246c515 |
| StoneVault               | 0x2ba50aca54da6b7c48ba30b93fe6acf242cbaf9c |
| Proposal                 | 0xc52d678f99bfc43ae777a16a79b78db571a3e2a1 |
| StrategyController       | 0xb9C779f6A9b845bb77DD0339b3c643F273CD208b |
| AssetVault               | 0x7c2521c59bd7ac9e4eca5dc9ec073aec49cf6ebe |
| MiningPool               | 0xfc7dD01f0967c7d3A5D34454D87db66C95B4f5A2 |


# Smart Contracts Address\_SBTC

## SBTC Contracts

<table><thead><tr><th width="297">Contract Name</th><th>Address</th></tr></thead><tbody><tr><td>SBTC (BNB Chain)</td><td>0x15469528C11E8Ace863F3F9e5a8329216e33dD7d</td></tr><tr><td>SBTCVault (BNB Chain)</td><td>0x3aa0670E24Cb122e1d5307Ed74b0c44d619aFF9b</td></tr><tr><td>SBTCLayerZeroAdapter (BNB Chain)</td><td>0x7122985656e38BDC0302Db86685bb972b145bD3C</td></tr><tr><td>SBTC (Ethereum)</td><td>0x094c0e36210634c3CfA25DC11B96b562E0b07624</td></tr><tr><td>SBTCVault (Ethereum)</td><td>0x7dBAC0aA440A25D7FB43951f7b178FF7A809108D</td></tr><tr><td>SBTCLayerZeroAdapter (Ethereum)</td><td>0x3f690f43a9fCA689829A22bf925c89B7a48ca57F</td></tr><tr><td>SBTC (Scroll)</td><td>0xE630Abc6a480AC27270Fa9Ce615bFA5917e85525</td></tr><tr><td>SBTCLayerZeroAdapter (Scroll)</td><td>0x4F9F1333cfFA3e0dcA98736E260442a86D918501</td></tr><tr><td>SBTC (Zircuit)</td><td>0x438fA5A9B1d57165E6ea1005Ee035d6554b0b54F</td></tr><tr><td>SBTCLayerZeroAdapter (Zircuit)</td><td>0xaCD6510CE275F86C651e9743Ea744141c7072183</td></tr><tr><td>SBTC (BOB Chain)</td><td>0x80137510979822322193FC997d400D5A6C747bf7</td></tr><tr><td>SBTCLayerZeroAdapter (BOB Chain)</td><td>0xD2012fc1B913cE50732ebcaa7E601fe37Ac728C6</td></tr><tr><td>SBTC (Aptos)</td><td>0x5dee1d4b13fae338a1e1780f9ad2709a010e824388efd169171a26e3ea9029bb::stakestone_bitcoin::StakeStoneBitcoin</td></tr></tbody></table>


# Smart Contracts Address\_STONEBTC

<table><thead><tr><th width="271">Contract Name</th><th>Address</th></tr></thead><tbody><tr><td>STONEBTC（Ethereum）</td><td>0x2D83F5BfC83cF0B09B8884101C015FA9c74c32F3</td></tr><tr><td>OracleConfigurator</td><td>0x6cD42e64630d25406bFC51CcA65cFfa7Cd495FB1</td></tr><tr><td>StoneBTCVault</td><td>0x1fC603779DC6b4866769A58067777D2C52628226</td></tr><tr><td>SBTC</td><td>0x094c0e36210634c3CfA25DC11B96b562E0b07624</td></tr><tr><td>LBTC</td><td>0x8236a87084f8B84306f72007F36F2618A5634494</td></tr></tbody></table>


# StakeStone API References

This page describes detailed technical interfaces on StakeStone, including interface definitions, listed parameters, return values and call samples of different programming languages and environments.

Before we proceed, it is essential to have a basic understanding of programming concepts related to blockchain. This includes familiarity with Ethereum and its associated concepts such as smart contracts, and the Solidity programming language, as well as popular development environments like Remix, Truffle, Hardhat, and others.

## Vault-Related

### Deposit ETH to vault

**Description**

Make a deposit to StakeStone vault, and the caller will get STONE tokens as the vault shares.

**Function Description**

<table><thead><tr><th width="215.5">Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity"><strong>    function deposit()
</strong>        external
        payable
        nonReentrant
        returns (uint256 mintAmount)
</code></pre></td></tr><tr><td>Function Selector</td><td>0xd0e30db0</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td>mintAmount, the STONE tokens minted</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">    event Deposit(
        address indexed account,
        uint256 amount,
        uint256 mint,
        uint256 round
    );
</code></pre></td></tr><tr><td>Event Signature</td><td>0x36af321ec8d3c75236829c5317affd40ddb308863a1236d2d277a4025cccee1e</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "deposit",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "mintAmount",
      "type": "uint256"
    }
  ],
  "stateMutability": "payable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [    {
      "inputs": [],
      "name": "deposit",
      "outputs": [
        {
          "internalType": "uint256",
          "name": "mintAmount",
          "type": "uint256"
        }
      ],
      "stateMutability": "payable",
      "type": "function"
    }];

// Deposit 1 Ether.
const DEPOSIT_AMOUNT = 1e18;

var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.deposit().send({
    from: "CALLER_ADDRESS",
    value: BigNumber(DEPOSIT_AMOUNT).toString(10)
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Make a deposit to vault

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Make a deposit transaction to StakeStone vault.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                           |
| ----------------------------------------- | ------ | ----------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                                 |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                             |
| params<mark style="color:red;">\*</mark>  | Array  | the signed transaction data coerced into string array |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id    |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Make a withdrawal request from vault

**Description**

Make a withdrawal request from Vault. User could retrieve ETH principal and yields from vault after vault has been settled.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function requestWithdraw(uint256 _shares) external
</code></pre></td></tr><tr><td>Function Selector</td><td>0x745400c9</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td><strong>uint256 _shares</strong>, the STONE amount to withdraw; actual number multiplied by 1E18</td></tr><tr><td>Return Value</td><td>None.</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">    event InitiateWithdraw(
        address indexed account,
        uint256 shares,
        uint256 round
    );
</code></pre></td></tr><tr><td>Event Signature</td><td>0x0c53c82ad07e2d592d88ece3b066777dd60f1118e2a081b380efc4358f0d9e2a</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "uint256",
      "name": "_shares",
      "type": "uint256"
    }
  ],
  "name": "requestWithdraw",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
      "inputs": [
        {
          "internalType": "uint256",
          "name": "_shares",
          "type": "uint256"
        }
      ],
      "name": "requestWithdraw",
      "outputs": [],
      "stateMutability": "nonpayable",
      "type": "function"
    }];

// Withdraw 1 STONE.
const WITHDRAW_AMOUNT = 1e18;

var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.requestWithdraw(WITHDRAW_AMOUNT).send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Make a withdrawal request from vault.&#x20;

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Make a withdrawal request transaction from vault.&#x20;

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                           |
| ----------------------------------------- | ------ | ----------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                                 |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                             |
| params<mark style="color:red;">\*</mark>  | Array  | the signed transaction data coerced into string array |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id    |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Cancel withdrawal request

**Description**

Cancel a previous withdrawal request to get pending STONE back.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function cancelWithdraw(uint256 _shares) external
</code></pre></td></tr><tr><td>Function Selector</td><td>0x9f01f7ba</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td><strong>uint256 _shares</strong>, the STONE amount to cancel; actual number multiplied by 1E18</td></tr><tr><td>Return Value</td><td>None.</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">    event CancelWithdraw(
        address indexed account,
        uint256 amount,
        uint256 round
    );
</code></pre></td></tr><tr><td>Event Signature</td><td>0x39e2e01794006bc1f63835af5c05db790beca4bfb40de3f02cc3ddf22dccc0fb</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "uint256",
      "name": "_shares",
      "type": "uint256"
    }
  ],
  "name": "cancelWithdraw",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "uint256",
      "name": "_shares",
      "type": "uint256"
    }
  ],
  "name": "cancelWithdraw",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}];

// Cancel 1 STONE's withdrawal.
const STONE_AMOUNT = 1e18;

var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.cancelWithdraw(STONE_AMOUNT).send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Cancel withdrawal request

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Cancel a former withdrawal request to get pending STONE back.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                           |
| ----------------------------------------- | ------ | ----------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                                 |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                             |
| params<mark style="color:red;">\*</mark>  | Array  | the signed transaction data coerced into string array |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id    |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query current STONE price

**Description**

Query the real-time STONE price(quoted by ETH price).

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function currentSharePrice() public returns (uint256 price)
</code></pre></td></tr><tr><td>Function Selector</td><td>0x28a79576</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 price</strong>, the price of STONE</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "currentSharePrice",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "price",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "currentSharePrice",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "price",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}];

var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.currentSharePrice().call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query current STONE price

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Query the real-time STONE price(quoted by ETH price).

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query historical STONE price

**Description**

Query the historical STONE price by settlement round (quoted by ETH price).

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function roundPricePerShare(uint256 _round) public returns (uint256 price)
</code></pre></td></tr><tr><td>Function Selector</td><td>0x87153eb1</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 price</strong>, the price of STONE</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "name": "roundPricePerShare",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [    {
      "inputs": [],
      "name": "deposit",
      "outputs": [
        {
          "internalType": "uint256",
          "name": "mintAmount",
          "type": "uint256"
        }
      ],
      "stateMutability": "payable",
      "type": "function"
    }];

// Round 1.
const ROUND = 1;

var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.roundPricePerShare(ROUND).call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query historical STONE price

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Query the historical STONE price by settlement round (quoted by ETH price).

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the transaction data coerced into string array     |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query latest settlement round

**Description**

Query the latest settlement round of StakeStone vault.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function latestRoundID() public returns (uint256 price)
</code></pre></td></tr><tr><td>Function Selector</td><td>0xf76339dc</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 round</strong>, the latest settlement round</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "latestRoundID",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "latestRoundID",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.latestRoundID().call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query latest settlement round

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Query the latest settlement round of StakeStone vault.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query withdraw fee rate

**Description**

Query withdraw fee rate of StakeStone vault(multiplied by 1E6).

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StoneVault contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StoneVault.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function withdrawFeeRate() public returns (uint256 price)
</code></pre></td></tr><tr><td>Function Selector</td><td>0xea99e689</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 rate</strong>, withdraw fee rate(multiplied by 1E6)</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "withdrawFeeRate",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StoneVault contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "withdrawFeeRate",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "",
      "type": "uint256"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.withdrawFeeRate().call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query withdraw fees

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Query withdraw fee rate of StakeStone vault(multiplied by 1E6).

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

## Strategy-Related

### Query all strategies of the portfolio

**Description**

Get all smart contract address of strategies.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StrategyController contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StrategyController.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function getStrategies() public view
    returns (address[] memory addrs, uint256[] memory portions)
</code></pre></td></tr><tr><td>Function Selector</td><td>0xb49a60bb</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>address[] memory addrs</strong>, the array of strategy address<br><strong>uint256[] memory portions</strong>, the array of the portions of each strategy</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "getStrategies",
  "outputs": [
    {
      "internalType": "address[]",
      "name": "addrs",
      "type": "address[]"
    },
    {
      "internalType": "uint256[]",
      "name": "portions",
      "type": "uint256[]"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StrategyController contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "getStrategies",
  "outputs": [
    {
      "internalType": "address[]",
      "name": "addrs",
      "type": "address[]"
    },
    {
      "internalType": "uint256[]",
      "name": "portions",
      "type": "uint256[]"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.getStrategies().send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query all strategies of the portfolio

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Get all smart contract address of strategies.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query ethers deployed on all strategies

**Description**

Get ethers amount deployed on all strategies.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StrategyController contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StrategyController.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function getAllStrategiesValue() public returns (uint256 _value)
</code></pre></td></tr><tr><td>Function Selector</td><td>0xb49a60bb</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 value</strong>, ether amount(multiplied by 1E18)</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "getAllStrategiesValue",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "_value",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StrategyController contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "getAllStrategiesValue",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "_value",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.getAllStrategiesValue().send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query ethers deployed on all strategies

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Get ethers amount deployed on all strategies.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query ethers deployed on certain strategy

**Description**

Get ether amount deployed on certain strategy.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>StrategyController contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>StrategyController.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">    function getStrategyValue(
        address _strategy
    ) public returns (uint256 _value) 
</code></pre></td></tr><tr><td>Function Selector</td><td>0x9841ab00</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>uint256 value</strong>, ether amount(multiplied by 1E18)</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "_strategy",
      "type": "address"
    }
  ],
  "name": "getStrategyValue",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "_value",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need StrategyController contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "address",
      "name": "_strategy",
      "type": "address"
    }
  ],
  "name": "getStrategyValue",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "_value",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.getStrategyValue().send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query ethers deployed on certain strategy

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Get ether amount deployed on certain strategy.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

## Vote-Related

### Query all proposals

**Description**

Get all smart contract address of proposals.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>Proposal contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>Proposal.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function getProposals() public view returns (address[] memory addrs)
</code></pre></td></tr><tr><td>Function Selector</td><td>0x62564c48</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td>None.</td></tr><tr><td>Return Value</td><td><strong>address[] memory addrs</strong>, the array of proposal address</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [],
  "name": "getProposals",
  "outputs": [
    {
      "internalType": "address[]",
      "name": "addrs",
      "type": "address[]"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need Proposal contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [],
  "name": "getProposals",
  "outputs": [
    {
      "internalType": "address[]",
      "name": "addrs",
      "type": "address[]"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.getProposals().call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query all proposals

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Get all smart contract address of proposals.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Query vote info on certain proposal

**Description**

Get the proposal details.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>Proposal contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>Proposal.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function proposalDetails(address _proposal) public view 
  returns (
        address proposer,
        uint256 deadline,
        uint256 support,
        uint256 oppose,
        uint256 executedTime,
        bytes data
  )
</code></pre></td></tr><tr><td>Function Selector</td><td>0x3b23c36d</td></tr><tr><td>Invocation Type</td><td>Ethereum Call</td></tr><tr><td>Passing Parameters</td><td><strong>address _proposal</strong>, proposal address</td></tr><tr><td>Return Value</td><td><strong>address proposal</strong>, the address propose the proposal<br><strong>uint256 deadline</strong>, the deadline of voting period<br><strong>uint256 support</strong>, the vote amount of supporting the proposal<br><strong>uint256 oppose</strong>, the vote amount of opposing the proposal<br><strong>uint256 executedTime</strong>, the timestamp of executing the proposal<br><strong>bytes data</strong>, proposal data</td></tr><tr><td>Event Emitted</td><td>None.</td></tr><tr><td>Event Signature</td><td>None.</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "",
      "type": "address"
    }
  ],
  "name": "proposalDetails",
  "outputs": [
    {
      "internalType": "address",
      "name": "proposer",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "deadline",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "support",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "oppose",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "executedTime",
      "type": "uint256"
    },
    {
      "internalType": "bytes",
      "name": "data",
      "type": "bytes"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need Proposal contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "address",
      "name": "",
      "type": "address"
    }
  ],
  "name": "proposalDetails",
  "outputs": [
    {
      "internalType": "address",
      "name": "proposer",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "deadline",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "support",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "oppose",
      "type": "uint256"
    },
    {
      "internalType": "uint256",
      "name": "executedTime",
      "type": "uint256"
    },
    {
      "internalType": "bytes",
      "name": "data",
      "type": "bytes"
    }
  ],
  "stateMutability": "view",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.proposalDetails(PROPOSAL_ADDRESS).call({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Query vote info on certain proposal

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Get the proposal details.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_call"                                        |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Vote for a proposal

**Description**

Voting for a proposal by staking with STONE.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>Proposal contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>Proposal.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function voteFor(address _proposal, uint256 _poll, bool _flag) external
</code></pre></td></tr><tr><td>Function Selector</td><td>0x31547ea6</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td><strong>address _proposal</strong>, the proposal address<br><strong>uint256 _poll</strong>, the STONE amount will be staked which represents the voting power<br><strong>bool _flag</strong>, true represents the supporting of a proposal</td></tr><tr><td>Return Value</td><td>None.</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">event VoteFor(address proposal, uint256 poll, bool flag);
</code></pre></td></tr><tr><td>Event Signature</td><td>0xdf4863bb3c37bd8d486548a8abd33fb356c8536cbb1111b676b1810d64447544</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need Proposal contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.voteFor(PROPOSAL_ADDRESS, STONE_AMOUNT, true).send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Vote for a proposal

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Voting for a proposal by staking with STONE.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                          |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Retrieve STONEs voted for certain proposal

**Description**

Voting for a proposal by staking with STONE.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>Proposal contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>Proposal.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function voteFor(address _proposal, uint256 _poll, bool _flag) external
</code></pre></td></tr><tr><td>Function Selector</td><td>0x31547ea6</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td><strong>address _proposal</strong>, the proposal address<br><strong>uint256 _poll</strong>, the STONE amount will be staked which represents the voting power<br><strong>bool _flag</strong>, true represents the supporting of a proposal</td></tr><tr><td>Return Value</td><td>None.</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">event VoteFor(address proposal, uint256 poll, bool flag);
</code></pre></td></tr><tr><td>Event Signature</td><td>0xdf4863bb3c37bd8d486548a8abd33fb356c8536cbb1111b676b1810d64447544</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need Proposal contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.voteFor(PROPOSAL_ADDRESS, STONE_AMOUNT, true).send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Vote for a proposal

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Voting for a proposal by staking with STONE.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                          |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}

### Retrieve STONEs voted for all proposals

**Description**

Voting for a proposal by staking with STONE.

**Function Description**

<table><thead><tr><th>Items</th><th>Description</th></tr></thead><tbody><tr><td>Contract Address</td><td>Proposal contract (referenced by <a href="/stakestone/developers/smart-contracts-address_stone">Smart Contracts Address section</a>)</td></tr><tr><td>Contract Name</td><td>Proposal.sol</td></tr><tr><td>Function Name</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">function voteFor(address _proposal, uint256 _poll, bool _flag) external
</code></pre></td></tr><tr><td>Function Selector</td><td>0x31547ea6</td></tr><tr><td>Invocation Type</td><td>Ethereum Transaction</td></tr><tr><td>Passing Parameters</td><td><strong>address _proposal</strong>, the proposal address<br><strong>uint256 _poll</strong>, the STONE amount will be staked which represents the voting power<br><strong>bool _flag</strong>, true represents the supporting of a proposal</td></tr><tr><td>Return Value</td><td>None.</td></tr><tr><td>Event Emitted</td><td><p></p><pre class="language-solidity"><code class="lang-solidity">event VoteFor(address proposal, uint256 poll, bool flag);
</code></pre></td></tr><tr><td>Event Signature</td><td>0xdf4863bb3c37bd8d486548a8abd33fb356c8536cbb1111b676b1810d64447544</td></tr></tbody></table>

**ABI Description**

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

**Samples**

<pre class="language-javascript"><code class="lang-javascript"><strong>// Javascript example
</strong><strong>var Web3 = require('web3');
</strong>const BigNumber = require('bignumber.js');

const  web3 = new Web3("RPC Endpoint Url");

// Need Proposal contract address
const CONTRACT_ADDRESS = "";
const ABI = [{
  "inputs": [
    {
      "internalType": "address",
      "name": "_proposal",
      "type": "address"
    },
    {
      "internalType": "uint256",
      "name": "_poll",
      "type": "uint256"
    },
    {
      "internalType": "bool",
      "name": "_flag",
      "type": "bool"
    }
  ],
  "name": "voteFor",
  "outputs": [],
  "stateMutability": "nonpayable",
  "type": "function"
}];


var contract = new web3.eth.Contract(ABI, CONTRACT_ADDRESS);

contract.methods.voteFor(PROPOSAL_ADDRESS, STONE_AMOUNT, true).send({
    from: "CALLER_ADDRESS"
}, function(error, result){
    if(!error) {
      console.log('Response:', result);
    } else {
      console.log(error);
    }
});
</code></pre>

HTTP Request Example

## Vote for a proposal

<mark style="color:green;">`POST`</mark> `(RPC Endpoint)`

Voting for a proposal by staking with STONE.

\
More details on how to send a transaction via RPC endpoint could be found here, <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_sendrawtransaction>

#### Request Body

| Name                                      | Type   | Description                                        |
| ----------------------------------------- | ------ | -------------------------------------------------- |
| jsonrpc<mark style="color:red;">\*</mark> | String | "2.0"                                              |
| method<mark style="color:red;">\*</mark>  | String | "eth\_sendRawTransaction"                          |
| params<mark style="color:red;">\*</mark>  | Array  | the call data coerced into string array            |
| id<mark style="color:red;">\*</mark>      | Number | request sequence id, you could use timestamp as id |

{% tabs %}
{% tab title="200: OK Success response." %}

```
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "TRANSCACTION HASH with 0x prefix"
}
```

{% endtab %}
{% endtabs %}


# Cross-chain Interfaces

## Token Transfer

#### Function

```solidity
function sendFrom(
  address _from, 
  uint16 _dstChainId, 
  bytes calldata _toAddress, 
  uint _amount, 
  address payable _refundAddress, 
  address _zroPaymentAddress, 
  bytes calldata _adapterParams
) public
```

#### ABI

```json
{
  "inputs": [
    {
      "internalType": "address",
      "name": "_from",
      "type": "address"
    },
    {
      "internalType": "uint16",
      "name": "_dstChainId",
      "type": "uint16"
    },
    {
      "internalType": "bytes",
      "name": "_toAddress",
      "type": "bytes"
    },
    {
      "internalType": "uint256",
      "name": "_amount",
      "type": "uint256"
    },
    {
      "internalType": "address payable",
      "name": "_refundAddress",
      "type": "address"
    },
    {
      "internalType": "address",
      "name": "_zroPaymentAddress",
      "type": "address"
    },
    {
      "internalType": "bytes",
      "name": "_adapterParams",
      "type": "bytes"
    }
  ],
  "name": "sendFrom",
  "outputs": [],
  "stateMutability": "payable",
  "type": "function"
}
```

\`\_dstChainId\` list could find here: <https://layerzero.gitbook.io/docs/technical-reference/mainnet/supported-chain-ids>&#x20;

## Fetch STONE Price

#### Function

```solidity
function tokenPrice() public returns (uint256 price)
```

#### ABI

```solidity
{
  "inputs": [],
  "name": "tokenPrice",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "price",
      "type": "uint256"
    }
  ],
  "stateMutability": "nonpayable",
  "type": "function"
}
```

## Price Feeding

#### Function

```solidity
function updatePrice(
    uint16 _dstChainId,
    bytes memory _toAddress
) public payable returns (uint256 price) 
```

#### ABI

```solidity
{
  "inputs": [
    {
      "internalType": "uint16",
      "name": "_dstChainId",
      "type": "uint16"
    },
    {
      "internalType": "bytes",
      "name": "_toAddress",
      "type": "bytes"
    }
  ],
  "name": "updatePrice",
  "outputs": [
    {
      "internalType": "uint256",
      "name": "price",
      "type": "uint256"
    }
  ],
  "stateMutability": "payable",
  "type": "function"
}
```


# Addendum

The following section shows all articles and papers used in StakeStone's documents.


# References

* RPC References on Ethereum: <https://ethereum.org/en/developers/docs/apis/json-rpc>
* Solidity Documentation: <https://docs.soliditylang.org/>
* Truffle Documentation: <https://www.trufflesuite.com/docs>
* RPC Endpoint List: <https://chainlist.org/>&#x20;
* LayerZero Introduction: <https://layerzero.gitbook.io/docs/>


# Audits & Security

## STONEUSD

### Quantstamp

**Audit #1**

**Time:** 2025.10.02 - 2025.10.09

**Scope:** STONEUSD full scope

**Link:**&#x20;

[**https://certificate.quantstamp.com/full/stake-stone-tokenized-vault/aa7fd663-908f-49c5-bb62-eac2463f57f1/index.html**](https://certificate.quantstamp.com/full/stake-stone-tokenized-vault/aa7fd663-908f-49c5-bb62-eac2463f57f1/index.html)

**Report:**

{% file src="/files/Lxjv0Aqx2DiLsjMZBzID" %}

## STONE (ETH)

### Quantstamp

**Audit #1**

**Time:** 2024.06.24 - 2024.07.12

**Scope:** Full Scope Audit

**Link:**&#x20;

[**https://certificate.quantstamp.com/full/stake-stone/4b7cbc5e-5595-4ac4-ac36-176f43ee9adf/index.html**](https://certificate.quantstamp.com/full/stake-stone/4b7cbc5e-5595-4ac4-ac36-176f43ee9adf/index.html)

**Report:**

{% file src="/files/vLCxFkvKEdkVZmz1qFvN" %}

### SlowMist

**Audit #1**

**Time:** 2023.12.07 - 2023.12.18

**Report:**

{% file src="/files/PRDOGyMb5XtYHqpoaWRx" %}

**Audit #2**

**Time:** 2024.03.07 - 2024.03.11

**Link:** <https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/SlowMist%20Audit%20Report%20-%20StakeStone%20-%20Restaking_en-us.pdf>

**Report:**&#x20;

{% file src="/files/inZHMz0axW4CkOjLsChD" %}

**Audit #3**

**Time:** 2024.05.06 - 2024.05.07

**Report:**&#x20;

{% file src="/files/Gk2UWnNhi0XYFAjAlyJw" %}

**Audit #4**

**Time:** 2024.06.24

**Link:** <https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/SlowMist_Audit_Report_StakeStone_NativeLendingETHStrategy%26Symbi_en-us.pdf>\
**Report:**

{% file src="/files/a2I05p0NQUBB0x6vBCcN" %}

**Audit #5**&#x20;

**Time:** 2024.07.09

**Link:**&#x20;

<https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/SlowMist_Audit_Report_StakeStone_SymbioticDepositWBETHStrategy_en-us.pdf>

**Report:**

{% file src="/files/LqaUsogwOFYAZpHq9ewN" %}

**Audit #6 (STONEBTC)**

**Link:**

<https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/STONE%20BTC%20Vault%20-%20SlowMist%20Audit%20Report.pdf>

\
**Audit #7 (STONE Bera Vault)**

**Link:**&#x20;

<https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/Stone%20Bera%20Vault%20-%20SlowMist%20Audit%20Report.pdf>

**Audit #8 (SBTC Bera Vault)**

**Link:**

<https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/SBTC%20Bera%20Vault%20-%20SlowMist%20Audit%20Report.pdf>

### Secure3

**Audit #1**

**Time:** 2023.03.18

**Report:**&#x20;

{% file src="/files/kfqnJygvce4JL7aiJwph" %}

**Audit #2**

**Time:** 2023.08.14

**Link:** <https://github.com/Secure3Audit/Secure3Academy/blob/main/audit_reports/StakeStone/StakeStone_final_Secure3_Audit_Report.pdf>

**Report:** [](<https://veridise.com/audits/&#xD;&#xA;&#xD;&#xA;https://f8t2x8b2.rocketcdn.me/wp-content/uploads/2023/12/VAR-StakeStone-231208-2.pdf&#xD;&#xA;>)

{% file src="/files/KyGlbiJZ06e7LWCKfLOJ" %}

### Veridise&#x20;

**Audit #1**

**Time:** 2023.12.08 - 2023.12.15

**Link:**

\[<https://veridise.com/audits/>\\

\
<https://f8t2x8b2.rocketcdn.me/wp-content/uploads/2023/12/VAR-StakeStone-231208-2.pdf> <br>]\(<https://veridise.com/audits/&#xD;&#xA;&#xD;&#xA;https://f8t2x8b2.rocketcdn.me/wp-content/uploads/2023/12/VAR-StakeStone-231208-2.pdf&#xD;&#xA;>)

**Report:**&#x20;

{% file src="/files/H6KzBsgo86wmDYJ8Qzrl" %}

## SBTC

### QuantStamp&#x20;

**Audit #1**

**Link:**

[**https://certificate.quantstamp.com/full/stake-stone-stone-btc-and-vault/5fbbae75-0726-40d4-ad39-15491f27b400/index.html**](https://certificate.quantstamp.com/full/stake-stone-stone-btc-and-vault/5fbbae75-0726-40d4-ad39-15491f27b400/index.html)

### SlowMist

**Audit #1**

**Link:**

{% embed url="<https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/STONE%20BTC%20-%20SlowMist%20Audit%20Report_en-us.pdf>" %}

## STONEBTC

### SlowMist

**Audit #1**

**Link:**

[**https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/STONE%20BTC%20Vault%20-%20SlowMist%20Audit%20Report.pdf**](https://github.com/slowmist/Knowledge-Base/blob/master/open-report-V2/smart-contract/STONE%20BTC%20Vault%20-%20SlowMist%20Audit%20Report.pdf)

**Report:**&#x20;

{% file src="/files/DDoIbSZb8YmJa0lXuFCY" %}

## STO (token)

### SlowMist

**Audit #1**

**Report:**&#x20;

{% file src="/files/c3xYlBtAzkGxedavTxkM" %}


# Bug Bounty Program

StakeStone believes in the power of community to ensure security.&#x20;

Our bug bounty is currently live on Immunifi, for more info or to submit a bug, click [here](https://immunefi.com/bug-bounty/stakestone/information/).&#x20;


# Risks

Last Updated: 1st Sep. 2023

StakeStone is an innovative system that combines multiple DeFi protocols and assets, aiming to provide users with a one-stop staking experience with optimized risk-adjusted staking yields. It also offers a better yield-bearing asset option for developers. However, despite our best efforts, there are inherent risks associated with StakeStone, including vulnerabilities related to smart contracts, market dynamics, and third-party assets and protocols. These vulnerabilities may be exploited and pose potential risks to StakeStone users.

We believe it is essential to summarize the potential risks that users may encounter when using StakeStone. We also encourage you to explore additional potential risk factors and make decisions on whether and how to use StakeStone based on your own assessment and risk tolerance. StakeStone Protocol will not assume responsibility for any fund losses, regardless of the circumstances.

The list of risks outlined below is not exhaustive, as specific risk factors can change over time with evolving market conditions and industry developments. Therefore, we will periodically update this risk summary. Using a StakeStone product indicates that you have read and accept all risks associated with the StakeStone product, including but not limited to those described herein.

### SMART CONTRACT RISKS

Smart contract risk is one of the primary threats faced by DeFi, and while StakeStone's contracts undergo audits by well-respected and professional auditors and are open source, it's crucial to acknowledge that no contract can ever be completely risk-free. Despite our best intentions to prioritize user safety and multiple rounds of testing before release, there may still be potential vulnerabilities or logic errors that could be exploited, resulting in the loss of user funds.

To keep pace with the rapid changes in the market and technology and to ensure the security of user assets and the competitiveness of our product, the StakeStone team may make adjustments to certain parameters and settings within the contract or update the code. By using StakeStone, you agree to assume these risks and accept any changes the team may implement in the contract.

StakeStone has plans to introduce additional audits in the future and undergo further institutional-level scrutiny to minimize this risk as much as possible. We also strongly recommend that you gain a comprehensive understanding of the various risks associated with smart contracts.

Audit Report: hub.com/Secure3Audit/Secure3Academy/blob/main/audit\_reports/StakeStone/StakeStone\_final\_Secure3\_Audit\_Report.pdf

### DEFI COMPOSABILITY RISKS (THIRD-PARTY PROTOCOLS AND PLATFORMS)

The ability to combine multiple protocols, like building with LEGO blocks, to provide users with higher yields and a more convenient experience is one of the charms of DeFi. StakeStone, based on various reputable protocols, aims to offer users more competitive yields. However, stacking multiple DeFi protocols also increases the complexity of the code and system, leading to greater risks. Additionally, connecting to multiple protocols can expose StakeStone to market risks, DAO governance risks, mechanism risks, oracle risks, and other potential issues that may affect the StakeStone protocol. Any problems with the protocols that StakeStone relies on could potentially result in losses for StakeStone users.

While StakeStone supports only well-established, battle-tested protocols that have managed substantial assets and performed well during crises, it is impossible to guarantee that all the protocols integrated into StakeStone will always function as intended. Therefore, we strongly recommend that users gain a better understanding of the protocols currently supported by StakeStone, including Lido, Rocket Pool, Balancer, Aura, and Maverick, and evaluate the risks associated with interacting with these protocols based on your personal preferences.

In the future, StakeStone may become compatible with additional blue-chip DeFi protocols. The addition of any new protocols will be proposed on-chain, publicly disclosed during a time lock period, and subject to open voting by STONE holders before implementation. All proposals will be announced, and we encourage you to set reminders to independently monitor the operation of StakeStone and exercise your rights as an STONE holder in a decentralized manner.

### UNDERLYING ASSET RISKS

The value of ETH and STONE minted in StakeStone is backed by a basket of underlying assets, including various LSTs (such as wstETH, rETH, frxETH) and DEX’s LP tokens. These assets are known for their strong performance and adequate liquidity. However, it's essential to be aware that each underlying asset carries counterparty risk. When these underlying assets experience significant changes, including but not limited to price decoupling, issues with operating organizations, or severe slashing, the value of STONE can also be affected.

To protect user assets in the event of extreme situations involving the underlying assets, StakeStone's contract includes an emergency rebalancing feature. This feature allows for the swapping of such assets for ETH and returning them to the StakeStone Vault in the event of significant risks associated with one or more underlying assets, without impacting the ownership of the assets. This function is designed to preserve user assets as much as possible while not moving assets away from their ownership.

### REBALANCE / ALLOCATION OPTIMIZATION RISKS

In pursuit of optimized risk-adjusted yields, funds in the StakeStone protocol are periodically reallocated and reconfigured among the currently supported protocols and assets. Any operations involving fund allocation require a proposal to be submitted in an on-chain format, disclosed during the Timelock phase, and executed only after receiving approval through a vote by STONE holders. However, reallocating funds may potentially lead to price impacts, which in turn can result in potential capital losses.

Nevertheless, StakeStone's smart contract incorporates a limit on the price impact caused by operations, which is set at 0.5%. Any operations that could result in losses exceeding 0.5% will not be executed, regardless of whether the losses are due to price impact or external malicious MEV attacks.

This limit is designed to mitigate the risk associated with significant price fluctuations during the reallocation process and protect the capital of STONE holders to a certain extent.

### CROSS-CHAIN RISKS

STONE is an omni-chain LST (Liquid Staking Token) that leverages Layerzero to seamlessly transmit asset and price information across various L2 (Layer 2) and sidechains. Currently, supported chains include Base, Linea, Mantle, Arbitrum, with plans for further expansion in the future. During the process of cross-chain transmission of asset and price information, users may encounter corresponding risks. It's important to note that different chains operate with distinct mechanisms and structures, resulting in varying levels of risk associated with each chain.

### STONE USE CASES RISKS

STONE is a developer-friendly LST asset with the potential for adoption by various protocols such as stablecoins, lending platforms, derivatives, and more. Protocols that support STONE as an underlying asset enable STONE holders to earn rewards by utilizing STONE within these platforms. However, it's essential to note that supporting STONE as an underlying asset is permissionless, and StakeStone cannot impose restrictions on the use cases of STONE. Using STONE in protocols outside of StakeStone may expose users' funds to risks. Therefore, we strongly advise users to thoroughly understand any protocol they intend to use STONE in and assess its associated risks before proceeding.

### REGULATORY RISKS

Cryptocurrency and DeFi remain at the forefront of technological innovation, and regulatory developments in this field are continually evolving. In extreme circumstances, it is possible that users may be unable to access StakeStone's products through the website frontend. However, users will still have the option to withdraw their funds by interacting directly with the smart contracts. This decentralized approach ensures that users can maintain control over their assets, even in challenging regulatory environments or unforeseen circumstances that may impact frontend access.


# Terms of Service

Effective Date: From 1st Sep. 2023 to 1st Sep. 2028

Please read on to acquaint yourself with the rules that oversee your utilization of our products, services, and applications, encompassing, though not limited to, our web interface hosted at [stakestone.io](http://stakestone.io/) ("Website") and our associated mobile application(s) collectively known as the "Services."

These Terms of Service (referred to herein as the "Terms") stand as a legally binding agreement between you and StakeStone Protocol. In these Terms, pronouns such as "we," "us," or "our" also pertain to StakeStone. Your consent to and acknowledgment of all the provisions contained within these Terms is imperative; otherwise, you don’t have the right to use our services and product. Your engagement with the Services in any manner signifies your acceptance of the entirety of these Terms, and they shall continue to remain in force throughout the duration of your usage. These Terms encompass the stipulations within this document, as well as those outlined in our Risk Summaries, and any other terms and conditions that may be cross-referenced or integrated into these Terms periodically.

We strictly adheres to regulatory policies in various countries/regions and does not provide services to users from the countries and districts including but not limited to United States, Mainland China, and Hong Kong. By accessing or using our protocol, you acknowledge and agree that you are not a citizen in any prohibited localities. Users are advised to utilize our product in compliance with the applicable laws and regulations of their respective jurisdictions. If the laws and regulations of your country/region do not support your usage of StakeStone, we regretfully cannot offer our services to you. By using this site, you agree and promise that under the laws of the jurisdiction in which you reside and are currently located, you have the legal right to access this site and utilize its services.

IT IS IMPORTANT TO NOTE THAT THESE TERMS INCORPORATE AN ARBITRATION CLAUSE. BY AGREEING TO THESE TERMS, YOU EXPRESSLY CONSENT AND COMPREHEND THAT ANY DISPUTES ARISING UNDER THESE TERMS SHALL BE RESOLVED THROUGH BINDING ARBITRATION. ADDITIONALLY, YOU AFFIRMATIVELY AGREE AND COMPREHEND THAT YOUR ACCEPTANCE OF THIS AGREEMENT CONSTITUTES A VOLUNTARY RELINQUISHMENT OF YOUR ENTITLEMENT TO A TRIAL BY JURY OR PARTICIPATION IN A CLASS ACTION LAWSUIT OR JURY TRIAL.

### CHANGES TO OUR TERMS OF SERVICES

We are consistently dedicated to enhancing our Services; consequently, there may arise a necessity to modify these Terms together with the improvement of our Services. We reserve the right to effect changes to these Terms at any given point in time. This authority encompasses the suspension or cessation of specific facets of the Services, the introduction of novel features, the imposition of constraints on particular functionalities, or the restriction of access to segments or the entirety of the Services. Furthermore, we reserve the right to remove any content from the Services without prior notice, based on our sole discretion.

In the event you find yourself in disagreement with the updated Terms subsequent to any modifications, you have the right to reject. However, you will not be able to use the Service. If you use our services in any capacity following the implementation of an altered set of Terms, it denotes your concurrence with all the adjustments therein.

It is essential to underscore that, with the exception of modifications instituted by us as delineated herein, no other revisions to these Terms will possess legal validity unless they are documented in writing and bear the signatures of both you and us.

### ELIGIBILITY TO USE OUR SERVICES

In order to access our Services, you must possess the capacity to enter into a legally binding agreement with us. Accordingly, you affirm and guarantee that you have reached the legal age required to establish a binding contract. If you are not of legal age, you must have obtained consent from your parent or legal guardian to use the Services, and they must have agreed to these Terms on your behalf.

If you are agreeing to these Terms on behalf of an organization or entity, you assert and warrant that you possess the authority to accept these Terms on behalf of said organization or entity, and you are empowered to bind them to these Terms. In such cases, the terms "you" and "your" within these Terms (with the exception of this sentence) refer to that organization or entity. You are solely permitted to utilize the Services for your individual, personal use, and not on behalf of, or for the advantage of, any third party. This usage must strictly adhere to all relevant laws and regulations that pertain to you.

### USAGE OF OUR SERVICES

Our Services primarily consist of a web-hosted user interface on the Site and our corresponding mobile application(s). These platforms enable you to import an Ethereum wallet capable of storing and transferring specific supported Virtual Currency. Once you have connected a Wallet, you can utilize various features of our Services to manage your portfolio of Virtual Currencies and access and interact with supported decentralized protocols and decentralized applications.

Certain dapps associated with StakeStone may involve accessing Virtual Currency markets, or interfaces that facilitate complex financial transactions. We may also offer scripts, smart contract interactions, or other modules that enable the automation or combination of these intricate financial transactions. It is important to understand that your decision to interact with any of these systems or code is entirely your own, and we hold no control or responsibility for the outcomes of your transactions.

When you seek to execute a Virtual Currency transfer, to commence such transfer on our platform, you will need to initiate the transfer through your Wallet's interface or a web plug-in that interacts with our services. This process may necessitate the use of your private key or an alternative authentication method for Wallet access. It is important to acknowledge that we are legally entitled to rely upon the initiation of the transfer and are under no obligation to scrutinize or investigate its validity or accuracy. Consequently, you bear full responsibility for safeguarding your hardware devices, including your mobile phone, and any actions associated with these devices and your Wallet while using our services. Please be aware that we cannot be held accountable if another party gains access to your devices and authorizes a transaction after receiving a valid Transfer Initiation.

Regardless of your chosen method of authentication or Wallet access, it is important to understand that we will never have access to the Virtual Currency within your Wallet, nor will we store your private key or any analogous means of accessing your Wallet. Furthermore, we will never request such sensitive information. It is essential to note that we are unable to initiate a Virtual Currency transfer on your behalf.

We wish to clarify that we do not assume a fiduciary relationship or any associated obligations concerning decisions or actions made while utilizing your Wallet or our services. We bear no responsibility for any activities in which you engage while utilizing your Wallet. Additionally, we strongly recommend that you comprehend the inherent risks associated with our product and blockchain technology as a whole.

### LIMITATION OF LIABILITY

To the maximum extent permissible under relevant legislation, under no circumstances shall the owner or contributors to the Website be held liable for any forms of damages, including, but not confined to, indirect, incidental, punitive, or consequential damages of any kind. These damages encompass losses such as loss of utility, loss of earnings, business interruption, erosion of reputation, or data loss, all stemming from the utilization of the Product.

### INFORMATION DISCLAIMER

The information presented on the Website serves exclusively as an informational resource and should not be construed as investment counsel, financial, legal, regulatory, accounting, tax advice, or equivalent guidance. It is imperative that you refrain from interpreting any content on the Website as such.

Moreover, nothing contained within this Website should be viewed as a suggestion, whether emanating from us, our associates, or any third party, to either acquire or divest investments or engage in specific investment tactics or transactions. We urge you to consult your own professionals in areas such as investment, legal, and tax, suited to your unique circumstances and choices.

Our team administers the Website as a public service and explicitly disclaims all liability for damages, regardless of their nature, resulting from the utilization, referral to, or reliance upon any information found on the Website. Although the content within the Website is periodically refreshed, we do not guarantee the accuracy, comprehensiveness, or currentness of the information offered therein.

### WARRANTIES DISCLAIMER&#x20;

This product do not have any warranties of any kind, whether express or implied. This includes, but is not limited to, implied warranties of merchantability, fitness for a specific purpose, non-infringement, or any assurance of uninterrupted or error-free availability, accessibility, or utilization of the Website and/or any content, data, materials, or services provided herein.

The functionality of the product is not guaranteed and may be partially or fully disabled without prior notice. However, it is still possible to access funds by invoking contracts even when the front-end of the website is inaccessible.

### RISK ASSUMPTION AND DISCLAIMER

Virtual Currency and blockchain technology are innovative with inherent risks, including but not limited to smart contract risks, market risks, third-party risks, and more. This is particularly relevant when using decentralized finance (DeFi) decentralized applications (dapps) through our Services. While our aim is to make these dapps more accessible, it is your sole responsibility to engage in transactions that you fully comprehend and are comfortable with. You must willingly assume all risks when conducting transactions involving Virtual Currency through our Services and should refrain from participating in transactions that are beyond your understanding.

Certain dapps may involve intricate financial transactions with a high level of risk, and we cannot provide financial or technical guidance for these transactions. Although some of our Services may combine and automate multiple transactions to simplify the process, you are responsible for comprehending each underlying transaction if you choose to use these specific Services.

By utilizing our Services, you acknowledge and accept the substantial risks associated with Virtual Currency and transactions conducted on the Ethereum network. In addition to the mentioned risks, you also agree and understand that:

* This product (StakeStone) will not be liable for any losses, damages, or claims arising from events such as user errors, software issues with the product or related software or services, technical malfunctions, user security issues, actions or inactions of third parties.
* Security audits do not entirely eliminate risks. This product is not guaranteed to be entirely secure or free from bugs or viruses.


# STONEUSD Terms of Service

**Last Updated: January 12, 2026**

These Terms of Use (“Terms”) constitute a legally binding agreement between you (“User” or “You”) and Pebble Network Limited, a British Virgin Islands company with company number 2179471 (“Pebble,” “we,” “us,” or “our”).<br>

#### 1. Acceptance and Modification of Terms

1.1 By accessing, interacting with, or utilizing any aspect of the websites, application programming interfaces (APIs), software applications, smart contract interfaces, and related informational content (collectively, the “Services”) provided by or in connection with Pebble, you affirm that you have read, comprehended, and consent to be bound by these Terms and any documents expressly incorporated herein by reference, including our Privacy Policy.

1.2 Pebble reserves the right, in its sole discretion, to amend, supplement, or update these Terms from time to time. The “Last Updated” date at the top of these Terms will indicate the effective date of the most recent version. Your continued use of the Services following the posting of revised Terms constitutes your acceptance of the changes.<br>

#### 2. Service Description and Protocol Functionality

2.1 Nature of the Services. The Services provide a technological interface and informational framework to interact with the STONEUSD protocol (“Protocol”). The Services facilitate (i) direct interactions with the Protocol’s smart contracts for eligible users, and (ii) access to secondary market liquidity solutions.<br>

2.2 Characterization of STONEUSD. STONEUSD is a blockchain-based digital token representing a claim on a proportional share of the assets managed by the Protocol’s underlying smart contract system. The value of this claim, as quantified by the Exchange Rate, is variable and responds to the performance of the referenced asset portfolio.

2.3 Direct Protocol Interactions (Minting & Redemption). Access to the functionalities for directly creating (“Minting”) or dissolving (“Redemption” or “Redeeming”) STONEUSD with the Protocol is not permissionless. Such access is restricted to users who have successfully completed prescribed identity verification (“KYC/KYB”) and anti-money laundering (“AML”) procedures and have been granted explicit permission (“Whitelisting”). These interactions are executed based on the Protocol’s dynamically calculated exchange rate (“Exchange Rate”).

2.4 Secondary Market Interactions (Swapping). The Services may provide or integrate with third-party liquidity solutions to facilitate the permissionless exchange (“Swapping”) of STONEUSD on secondary markets. The price for such swaps is determined by the integrated liquidity providers and may differ from the Protocol’s Exchange Rate.

#### 3. User Eligibility, Representations, and Warranties

3.1 Geographic and Regulatory Restrictions. You are prohibited from accessing or using the Services if you are: (i) located in, incorporated in, or a resident of a jurisdiction where such access or use would be contrary to applicable law or regulation; or (ii) accessing the Services from a location that would subject Pebble or the Protocol to any licensing or regulatory requirement. We reserve the right to restrict or block access from any jurisdiction at our sole discretion. You are solely responsible for determining whether your use of the Services is lawful in your jurisdiction.

3.2 Sanctions Compliance. You represent and warrant that you are not, and are not acting on behalf of any person or entity, subject to economic or trade sanctions administered by any governmental authority.<br>

3.3 KYC/AML Obligations. For access to Minting and Redemption services, you agree to provide accurate and complete information as required for our KYC/KYB and AML checks, which may be performed by us or our designated third-party service providers. We reserve the right to deny, suspend, or terminate access to these services based on the results of such checks or your failure to cooperate.

3.4 General Compliance. You are solely responsible for ensuring your use of the Services complies with all laws, rules, and regulations applicable to you. Any digital assets used in connection with the Services must be derived from lawful sources.

#### 4. Fees and Costs

4.1 Platform Fee. Pebble may charge a platform fee for the provision and maintenance of the Services. This fee is accounted for within the performance calculations affecting the Exchange Rate and is not separately charged to the User. The applicable rate and structure are subject to change at Pebble’s discretion.<br>

4.2 Protocol Redemption Fee. Pebble reserves the right to impose a fee on direct Redemptions processed through the Protocol. Any such fee will be clearly disclosed to the user prior to the confirmation of the redemption transaction.

4.3 Third-Party Swap Fees. Transactions conducted through integrated swap services are subject to fees determined by the respective liquidity providers. These fees are separate from any fees charged by Pebble and will be displayed within the swap interface prior to execution.

4.4 Blockchain Network Fees. All blockchain transaction fees (e.g., gas costs) associated with your interactions, whether with the Protocol or swap services, are your sole responsibility.

#### 5. Intellectual Property Rights

All rights, title, and interest in and to the Services, including the underlying software, website content, logos, trademarks, and all intellectual property contained therein, are the exclusive property of Pebble and its licensors. Your use of the Services grants you no license or right to use any intellectual property except as expressly provided herein.

#### 6. Third-Party Dependencies and Services

The Services and the operation of the Protocol are inherently dependent on external systems and service providers (“Third-Party Services”). You acknowledge and agree that Pebble does not own, control, or operate these services and assumes no liability for their actions or failures. Key dependencies include, but are not limited to:

* Custodians & Exchanges: Digital assets are held with third-party custodians and traded on third-party digital asset exchanges.
* Trading Counterparties: Portfolio strategies are executed by independent trading teams or counterparties.
* Infrastructure Providers: Blockchain networks, oracle services, liquidity providers, and KYC/AML verification services.
* Developments or operational issues affecting any Third-Party Service may impact the functionality of the Services, including the updating of the Exchange Rate and the processing of minting or redemption requests.

#### 7. Risk Factors

Your engagement with the Services and decision to hold STONEUSD involve a comprehensive understanding and assumption of multiple risks, which include, but are not limited to:

Market and Performance Risk: The value of the underlying assets is subject to market fluctuations. The Exchange Rate may depreciate, and you may incur a partial or total loss of capital. Positive returns are not guaranteed.<br>

Technology and Operational Risk: The Services involve complex software. They may be susceptible to operational delays or disruptions due to software anomalies, smart contract vulnerabilities, or issues with supporting infrastructure (e.g., multi-signature schemes, oracles).

Counterparty and Custody Risk: The Protocol relies on third-party custodians to hold assets and exchanges to facilitate trades. These relationships carry inherent risks, including the potential for service disruption, financial difficulty, or operational challenges at these external entities. Furthermore, the performance of the Protocol is linked to the actions of independent trading teams, whose strategies may not always be successful.<br>

Liquidity and Redemption Risk: Direct redemption through the Protocol is subject to eligibility, processing times, and asset availability. Pebble may, in its reasonable discretion, delay or suspend redemptions to protect the integrity of the Protocol in the event of market stress, operational incidents, or regulatory considerations. Secondary market liquidity is provided by third parties and may vary.

Regulatory and Legal Risk: The regulatory landscape for digital assets is evolving and varies across jurisdictions. Future regulatory or enforcement actions could influence the availability or structure of the Services.

\
Systemic and Contagion Risk: Failures or issues in broader digital asset markets, blockchain networks, or major industry participants may adversely affect the Protocol and STONEUSD, regardless of its specific operations.

Tax Risk: The tax treatment of holding, minting, redeeming, or swapping STONEUSD is uncertain and varies by jurisdiction. You are solely responsible for determining and fulfilling any tax obligations arising from your use of the Services.<br>

#### 8. Disclaimer of Warranties and Limitation of Liability

8.1 Disclaimer. THE SERVICES ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, PEBBLE EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE.

8.2 No Guarantees. Pebble does not guarantee, represent, or warrant: (i) the uninterrupted, secure, or error-free operation of the Services; (ii) the accuracy or completeness of any information, including the Exchange Rate or projected yields, provided through the Services; or (iii) that STONEUSD will maintain any specific value or purchasing power.

8.3 Limitation of Liability. IN NO EVENT SHALL PEBBLE, ITS AFFILIATES, OR THEIR RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES, OR AGENTS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES, OR FOR ANY LOSS OF PROFITS, GOODWILL, DATA, OR OTHER INTANGIBLE LOSSES, ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE USE OF THE SERVICES.<br>

#### 9. Indemnification

You agree to defend, indemnify, and hold harmless Pebble and its affiliates from and against any claims, damages, obligations, losses, liabilities, costs, and expenses (including reasonable legal fees) arising from: (i) your use of the Services; (ii) your violation of these Terms; or (iii) your violation of any law or the rights of a third party.<br>

#### 10. Suspension and Termination

Pebble may, in its sole discretion, suspend or terminate your access to all or part of the Services immediately, without prior notice or liability, for any reason, including if you breach these Terms.

#### 11. Governing Law and Dispute Resolution

11.1 Governing Law. These Terms and any dispute arising out of or in connection with them shall be governed by and construed in accordance with the laws of the British Virgin Islands.

11.2 Arbitration. Any dispute, controversy, or claim arising out of or relating to these Terms, or the breach, termination, or invalidity thereof, shall be finally settled by confidential arbitration administered by the BVI International Arbitration Centre (BVI IAC) in accordance with its Arbitration Rules in force at the time of the commencement of the arbitration. The seat of arbitration shall be Road Town, Tortola, British Virgin Islands. The language of the arbitration shall be English. The arbitral tribunal shall consist of a sole arbitrator.

11.3 Waiver of Class Actions and Jury Trial. YOU AGREE TO RESOLVE DISPUTES ONLY ON AN INDIVIDUAL BASIS AND WAIVE ANY RIGHT TO PARTICIPATE IN A CLASS, CONSOLIDATED, OR REPRESENTATIVE ACTION. TO THE FULLEST EXTENT PERMITTED BY LAW, YOU WAIVE YOUR RIGHT TO A TRIAL BY JURY.

#### 12. General Provisions

12.1 Severability. If any provision of these Terms is held to be invalid or unenforceable, the remaining provisions will remain in full force and effect.<br>

12.2 Assignment. You may not assign your rights under these Terms without our prior written consent. We may assign our rights without restriction.<br>

12.3 Entire Agreement. These Terms constitute the entire agreement between you and Pebble regarding the Services and supersede all prior agreements.

<br>


# Airdrop Terms and Conditions

Last Revised on Sep 19, 2024

### StakeStone Airdrop&#x20;

#### TERMS & CONDITIONS

BY PARTICIPATING IN THE AIRDROP, INCLUDING BUT NOT LIMITED TO BY ENTERING A WALLET (AS DEFINED BELOW) PURSUANT TO THE TERMS AND PROCESSES DESCRIBED HEREIN, PARTICIPANT ACKNOWLEDGES THAT THEY HAVE READ, UNDERSTOOD, AND AGREED TO THESE AIRDROP TERMS & CONDITIONS IN THEIR ENTIRETY. THE PARTICIPANT IS RESPONSIBLE FOR MAKING ITS OWN DECISION IN RESPECT OF ITS PARTICIPATION IN THE AIRDROP AND ANY RECEIPT OF TOKENS. ANY PARTICIPATION IN THE AIRDROP IS SOLELY AT THE PARTICIPANT’S OWN RISK AND IT IS THE PARTICIPANT’S SOLE RESPONSIBILITY TO SEEK APPROPRIATE PROFESSIONAL, LEGAL, TAX, AND OTHER ADVICE IN RESPECT OF THE AIRDROP AND ANY RECEIPT OF THE TOKENS PRIOR TO PARTICIPATING IN THE AIRDROP AND PRIOR TO RECEIVING ANY TOKENS.

BY PARTICIPATING IN THE AIRDROP, THE PARTICIPANT EXPRESSLY ACKNOWLEDGES AND ASSUMES ALL RISKS RELATED THERETO, INCLUDING (WITHOUT LIMITATION) THE RISKS SET OUT BELOW. IN NO EVENT SHALL THE ORGANIZATION OR ANY ORGANIZATION PERSON BE HELD LIABLE IN CONNECTION WITH OR FOR ANY CLAIMS, LOSSES, DAMAGES, OR OTHER LIABILITIES, WHETHER IN CONTRACT, TORT, OR OTHERWISE, ARISING OUT OF OR IN CONNECTION WITH THE AIRDROP OR THE RECEIPT OF ANY TOKENS.

THE ORGANIZATION DOES NOT TAKE ANY RESPONSIBILITY FOR THE PARTICIPATION BY ANY PARTICIPANT IN THE AIRDROP. THE ORGANIZATION DOES NOT PROVIDE ANY RECOMMENDATION OR ADVICE IN RESPECT OF THE AIRDROP OR THE TOKENS. EACH PARTICIPANT PARTICIPATES IN THE AIRDROP AT ITS OWN RISK AND RECEIVES TOKENS AT ITS OWN RISK.

#### INTRODUCTION[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#introduction)

Welcome to the StakeStone airdrop!

These Token Airdrop Terms & Conditions (“Airdrop Terms”) govern the participation in and receipt of tokens (“STONE” or “Tokens”) through the airdrop program (“Airdrop”) organized by StakeStone, a Cayman Islands company, and its subsidiaries, including STONE BIT PTE LTD (collectively, “Organization”, “we” or “us”). By participating in the Airdrop, you (“Participant”) agree to be bound by these Airdrop Terms. These Airdrop Terms are supplemental to, and incorporate by reference, our general Terms of Service available at <https://docs.stakestone.io/stakestone> (“General Terms”). Defined terms used but not defined herein have the meaning set forth in the General Terms. The Airdrop, and your participation in it, is a Service as defined under the General Terms.

These Airdrop Terms govern your ability to use our Services in order to participate in the Airdrop. Please read these Airdrop Terms carefully, as they include important information about your legal rights. Please also read the General Terms carefully. By participating in the Airdrop, you are agreeing to these Airdrop Terms and the General Terms. If you do not understand or agree to these Airdrop Terms and the General Terms, please do not participate in the Airdrop.

SECTION 7 OF THE GENERAL TERMS CONTAINS AN ARBITRATION CLAUSE AND CLASS ACTION WAIVER. PLEASE REVIEW SUCH CLAUSES CAREFULLY BECAUSE THEY AFFECT YOUR RIGHTS. BY AGREEING TO THESE AIRDROP TERMS, YOU AGREE TO RESOLVE ALL DISPUTES RELATED TO THE AIRDROP THROUGH BINDING INDIVIDUAL ARBITRATION AND TO WAIVE YOUR RIGHT TO PARTICIPATE IN CLASS ACTIONS, CLASS ARBITRATIONS, OR REPRESENTATIVE ACTIONS, AS SET FORTH IN THE GENERAL TERMS. YOU HAVE THE RIGHT TO OPT-OUT OF THE ARBITRATION CLAUSE AND THE CLASS ACTION WAIVER AS EXPLAINED IN SECTION 7 OF THE GENERAL TERMS.

1. You represent and warrant that all information provided during the Airdrop process is true, accurate, and complete.
2. You agree and acknowledge that (a) solely you are responsible and liable for all taxes due in connection with your participation in the Airdrop; and (b) you should consult a tax advisor with respect to the tax treatment of Airdrop StakeStone in your jurisdiction.
3. You agree and acknowledge that you are responsible for complying with all applicable laws of the jurisdiction in which you reside or in which you are participating in the Airdrop and claiming Airdrop Tokens.
4. You agree that you are not (i) a Prohibited Person (as defined in the General Terms); (ii) directly or indirectly acting on behalf of a Prohibited Person; and (iii) located in or accessing the Services from a Prohibited Jurisdiction (as defined below). You agree that you will not use a virtual private network (“VPN”) or similar tool to circumvent any geo-blocking and/or other restrictions that we have implemented in connection with the Airdrop. Any such deliberate circumvention, or attempted circumvention, of our controls may permanently disqualify you from participation in the Airdrop, as determined in our discretion.
5. You agree and acknowledge that your participation in the Airdrop does not violate any applicable laws, including without limitation applicable economic and trade sanctions and export control laws and regulations, such as those administered and enforced by the EU, OFSI, OFAC, the U.S. Department of State, the U.S. Department of Commerce, the UN Security Council, and other relevant authorities.
6. You agree and acknowledge that the Organization reserves the right to require additional information from you and to enter, use, or share such information into or with a Screening Service Provider (as defined below), and its systems, tools, or functionalities, as the Organization deems appropriate in its sole discretion, including to reduce the risks of money laundering, terrorist financing, sanctions violations, or other potentially illicit activity, or as otherwise necessary to address laws and regulations that may be relevant to the Airdrop or the Tokens. You agree to provide complete and accurate information in response to any such requests. You agree and acknowledge that the Organization is not responsible and cannot be held liable for any losses, expenses, or delays resulting from inaccurate or incomplete information, and you agree to assume full responsibility for any and all risks associated therewith.
7. You agree and acknowledge that your participation in the Airdrop and claim of Airdrop StakeStone does not require or involve any form of purchase, payment, or tangible consideration from or to us, nor otherwise require or involve any acceptance of value by us from you. You agree and acknowledge that you (a) lawfully may receive Tokens for free via the Airdrop (other than gas fees or applicable taxes, if any, that may be due to third parties), (b) were not promised the Tokens or any tokens (whether via the Airdrop or otherwise); and (c) took no action in anticipation of, or in reliance on, receiving the Tokens or any tokens, the occurrence of an Airdrop, or potential participation in any Airdrop.
8. Your eligibility to receive Airdrop tokens or participate in the Airdrop is subject to our sole discretion. The Airdrop shall be conducted during a specified period, as determined by the Organization in its sole discretion and announced on its website, stakestone.io (the “Airdrop Period”). Participant must follow the instructions set forth in any Airdrop announcement and/or such other instructions as may be provided by the Organization from time to time to participate in the Airdrop. The number of Tokens allocated to each Participant will be determined by the Organization, in its sole discretion, and such allocation may vary among Participants. Tokens may be made available for claims after an initial period in which Participants can check eligibility for, but not claim, Airdrop StakeStone.
9. You agree and acknowledge that you are not entitled to receive any Airdrop StakeStone and/or to participate in the Airdrop based on any documentation, commentary, calculators, metrics, and/or points systems published or otherwise made known by third parties monitoring activities on the StakeStone Protocol (or any of its smart contracts) or providing third-party applications or services relating thereto (“Third-Party Publications and Services”). You have no claim to StakeStone based on such Third-Party Publications and Services. The Organization does not review, control, monitor, or confirm the accuracy of information that may be provided through Third-Party Publications or Services. You agree and acknowledge that you have not engaged, and will not engage, in any activities designed to obtain Airdrop StakeStone, including on the basis of, or in reliance on, Third-Party Publications and Services.
10. You agree that you are the legal owner of the Airdrop Address (as defined below) that you use to access or participate in the Airdrop and the Services and will not sell, assign, or transfer control of such address or the Tokens to third parties to circumvent any StakeStone lock-up period or to knowingly redistribute Tokens to a person, IP Address (as defined below), or Airdrop Address (as defined below) that would violate these Airdrop Terms if claimed directly by such person, IP Address, or Airdrop Address.
11. To participate in the Airdrop, you will need to enter an eligible Airdrop Address (as defined below) and/or connect a compatible third-party digital wallet (either, a “Wallet”). Failure to provide and connect an eligible Wallet may result in the forfeiture of Tokens. There may be technical limitations, delays, and/or transaction fees due or payable to third parties, such as gas fees on Ethereum transactions, to receive and/or claim Tokens through your Wallet.
12. By using a Wallet, you agree that you are using the Wallet in accordance with any terms and conditions of an applicable third-party provider of such Wallet. Wallets are not maintained or supported by, or associated or affiliated with, the Organization. When you interact with the Airdrop or other Services, as between the Organization and you, you retain control over your digital assets at all times. We do not control digital assets, including the StakeStone, in your Wallet, and we accept no responsibility or liability to you in connection with your use of a Wallet. We make no representations or warranties regarding how the Airdrop or other Services will operate with, or be compatible with, any specific Wallet. The private keys necessary to access and/or transfer the digital assets held in a Wallet are not known or held by the Organization. Any third party that may gain access to Participant’s login credential, private key, or third-party cloud or storage mechanism for such information may be able to misappropriate StakeStone and/or other digital assets held by Participant. The Organization has no ability to help you access or recover your private key and/or seed phrase for your Wallet. As between you and the Organization, solely you are responsible for maintaining the confidentiality of your private key, and solely you are responsible for any transaction signed with your private key. The Organization is not responsible for any loss associated with the Participant’s private key, digital wallet, vault, or other storage mechanism.
13. You agree and acknowledge that if you are unable to claim the Airdrop due to technical bugs, smart contract issues, gas fees, wallet incompatibilities, loss of access to a wallet or the key thereto, or for any other reason, you will have no recourse or claim against the Organization or any Organization Person. In any such cases, neither the Organization nor any Organization Person will bear any liability.
14. You agree and acknowledge that claiming the Airdrop may require interaction with, reliance on, or an integration with third-party products or services (e.g., a wallet or a network or blockchain) that we do not control. In the event that you are unable to access such products, services, or integrations, or if they fail for any reason, and you are unable to participate in the Airdrop or claim Airdrop StakeStone as a result, you will have no recourse or claim against us or any Organization Person; and neither we nor any Organization Person bear(s) any responsibility or liability to you.
15. You agree and acknowledge that your participation in the Airdrop is at your own risk. You agree and acknowledge that you have carefully reviewed, read, and understood the Risk Factors below.
16. Without limiting any terms in the General Terms, including but not limited to Section 6.4 therein, you agree that you shall defend, indemnify, and hold the Organization Persons harmless from and against any and all claims, actions, proceedings, investigations, demands, suits, costs, damages, losses, liabilities and expenses (including attorneys’ fees and costs, and fines or penalties imposed by any regulatory authority) incurred by the Organization Persons arising out of or in connection with: (a) your use of, or conduct in connection with, the Airdrop; (b) your breach or our enforcement of these Airdrop Terms, or (c) your violation of any applicable law, regulation, or rights of any third party. If you are obligated to indemnify any Organization Person hereunder, then you agree that the Organization (or, at its discretion, the applicable Organization Persons) will have the right, in its sole discretion, to control any action or proceeding and to determine whether the Organization wishes to settle, and if so, on what terms, and you agree to fully cooperate with the Organization in the defense or settlement of such claim. Your obligations under this indemnification provision will continue even after these Airdrop Terms have expired or been terminated.

#### ELIGIBILITY[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#eligibility)

1. The Organization, in its sole discretion, shall determine the eligibility criteria for participation in the Airdrop, including the amount of StakeStone to be distributed to eligible Participants that satisfy certain criteria. Different eligible Participants may receive different amounts of StakeStone in any particular Airdrop, depending on the criteria set forth by the Organization for such Airdrop. The Organization shall have no obligation to notify actual or potential Airdrop participants of the eligibility criteria for any Airdrop prior to, during, or after the claims are opened for such Airdrop.
2. The Organization reserves the sole and absolute right to disqualify any Participant or potential Participant it deems ineligible for an Airdrop (be it under these Airdrop Terms or by having determined that Participant engaged in any conduct that the Organization considers harmful, unlawful, inappropriate, or unacceptable). Such disqualification may be appropriate if the Organization determines, in its sole discretion, for example, that Participant may have used multiple addresses to obscure its identity or location or to attempt to game, cheat, or hack the Airdrop, Tokens, or the StakeStone protocol.
3. Participant has full legal capacity and authority to bind and agree to the Airdrop Terms. Participant is at least 18 years of age or is of legal age to form a binding contract under applicable laws. If Participant is acting as an employee or agent of a legal entity, and enters into the Airdrop Terms on behalf of the entity, Participant represents and warrants that Participant has all necessary rights and authorizations to do so.
4. The Organization has implemented a risk-based program applicable to the Airdrop and any related participation or claims through its website, stakestone.io , and any subdomains (“StakeStone Claims”). This program screens StakeStone Claims using data and tools provided by an independent blockchain analytics provider (“Screening Service Provider”), applying screening criteria that may extend beyond the requirements of applicable law. StakeStone Claims also are subject to geo-location and proxy detection controls to prevent access to our website by users that may be Prohibited Persons or located in a Prohibited Jurisdiction (as defined below). The Organization reserves the right to take such additional steps as it deems necessary or appropriate, in its sole discretion, to verify the identity and eligibility of any person.

The Organization may deny, in its sole discretion, any person, internet-protocol address (“IP Address”), and/or Ethereum or similar digital-asset, smart-contract, or protocol address (“Airdrop Address”) access to the StakeStone Claims website (or otherwise exclude such person, IP Address, or Airdrop Address from StakeStone Claims) based on data from the Organization’s Screening Service Provider when such data indicates such person, IP Address, or Airdrop Address may present heightened risks based on the Organization’s risk assessment framework (“Risk Assessment Framework”).

By using the Services and participating in any Airdrop:

a. You agree and acknowledge that your Airdrop Address will be screened and excluded from StakeStone Claims, at our sole discretion, if we detect threshold transactions between your Airdrop Address and another Ethereum or similar digital-asset, smart-contract, or protocol address associated with certain risk-exposure categories established by our Screening Service Provider.

b. You agree and acknowledge that your IP Address will be screened and excluded from StakeStone Claims if our geo-location controls detect that you may be located in a (a) Sanctioned Jurisdiction; (b) jurisdiction subject to heightened sanctions risks identified or enforced by certain countries, governments, or international authorities; or (c) jurisdiction otherwise considered high risk with respect to the Airdrop or otherwise (collectively, “Prohibited Jurisdictions”). You agree and understand that the Prohibited Jurisdictions are subject to change at our sole discretion without notice.

c. To avoid circumvention of our geo-location controls, the Organization has implemented proxy and VPN detection and blocking controls, which are designed to prevent StakeStone Claims by any person detected to be using VPN and similar proxy technologies.

#### USER INTERFACE DISCLAIMER[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#user-interface-disclaimer)

There is only one website for StakeStone Claims, which is the following: claims.stakestone.io&#x20;

Use of the website for StakeStone Claims and participation in the Airdrop is at the risk of the user. The Services are provided on an “as is'” and “as available” basis. The Organization expressly disclaims all warranties of any kind, whether express, implied, or statutory, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

The Organization makes no warranty that the Airdrop or the Services will meet your requirements or be uninterrupted, timely, secure, or error-free. The Organization makes no warranty that the results that may be obtained from access to or the use of Services will be accurate or reliable or that the quality of any products, services, applications, information, or other material purchased or obtained by you through the Services will meet your expectations.

By accessing and using the Airdrop or the Services, you represent and warrant that you (a) understand the risks inherently associated with using cryptographic and blockchain-based systems and (b) have a working knowledge of the usage, storage, and intricacies of digital assets, such as those, like StakeStone, following an Ethereum token standard (ERC-20). You further represent that you understand that markets for digital assets are highly volatile due to various factors, including adoption, speculation, technology, security, and regulation. You acknowledge and accept that the cost and speed of transacting with cryptographic and blockchain-based systems, such as Ethereum, are variable and may increase or decrease dramatically at any time. You acknowledge and accept the risk that your digital assets may have no value or lose some or all of their value during the Airdrop Period, any StakeStone lock-up period, or after. You understand that anyone can create a token, including fake versions of existing tokens and tokens that falsely claim to represent certain projects, entities, or people, and you acknowledge and accept the risk that you or others may mistakenly seek to claim or trade those or other tokens. You acknowledge that the Organization is not responsible for any of these variables or risks and cannot be held liable for any resulting losses that you experience, including losses while accessing or using the Airdrop or the Services. Accordingly, you understand and agree to assume full responsibility for all of the risks of accessing and using the Airdrop and the Services.

You expressly understand and agree that the Organization will not be liable for any indirect, incidental, special, consequential, exemplary damages, or damages for loss of profits, including damages for loss of goodwill, use, or data or other intangible losses (even if the Organization has been advised of the possibility of such damages), whether based on contract, tort, negligence, strict liability, or otherwise, resulting from: (a) the use or the inability to use the Airdrop or the Services; (b) the cost of procurement of substitute goods and services resulting from any goods, data, information, or services purchased or obtained or messages received or transactions entered into through or from the Airdrop or the Services; (c) unauthorised access to or alteration of your transmissions or data; (d) statements or conduct of any third party on the Services; (e) interruption or cessation of function related to our interface or website; (f) bugs, viruses, trojan horses, or the like that may be transmitted to or through the interface or website; (g) errors or omissions in, or loss or damage incurred as a result of the use of, any content made available through the interface or website; or (h) any other matter relating to the Airdrop or the Services.

#### NO PROFESSIONAL ADVICE AND NO FIDUCIARY DUTIES[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#no-professional-advice-and-no-fiduciary-duties)

All information provided on the website or through the Airdrop or the Services, or otherwise provided by the Organization, is for informational purposes only and is not and should not be construed as professional advice. You should not take, or refrain from taking, any action based on any information contained on the website or obtained through the Airdrop or the Services. Before you make any financial, legal, tax, or other decisions with respect to the Airdrop or the Services, you should seek independent, professional advice from an individual who is licensed and qualified in the area for which such advice would be appropriate.

These Airdrop Terms are not intended to, and do not, create or impose any fiduciary duties on us. To the fullest extent permitted by law, you acknowledge and agree that we owe no fiduciary duties or liabilities to you or any other party, and that to the extent any such duties or liabilities may exist at law or in equity, those duties and liabilities are hereby irrevocably disclaimed, waived, and eliminated. You further agree that the only duties and obligations that we owe you are those set out expressly in these Airdrop Terms.

#### LIMITATION OF LIABILITY AND INDEMNIFICATION[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#limitation-of-liability-and-indemnification)

You have reviewed with your professional legal and other advisors and agree with the Disclaimers, Limitations of Liability, and Indemnification provisions in the General Terms.

#### ENTIRE AGREEMENT[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#entire-agreement)

These Airdrop Terms and the General Terms contain the entire agreement between you and the Organization regarding the Airdrop and supersede all prior and contemporaneous understandings between the parties regarding the Airdrop. We may modify these Airdrop Terms from time to time in which case we will update the “Last Revised” date at the top of these Airdrop Terms. The updated Airdrop Terms will be effective as of the time of posting, or such later date as may be specified in the updated Airdrop Terms. Your continued access or participation in the Airdrop after the modifications have become effective will be deemed your acceptance of the modified Airdrop Terms.

#### SEVERABILITY[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#severability)

If any term, clause, or provision of these Airdrop Terms is held to be illegal, invalid, void, or unenforceable (in whole or in part), then such term, clause, or provision shall be severable from the Airdrop Terms without affecting the validity or enforceability of any remaining part of that term, clause, or provision, or any other term, clause, or provision in the Airdrop Terms, which will otherwise remain in full force and effect. Any invalid or unenforceable provisions will be interpreted to affect the intent of the original provisions. If such construction is not possible, the invalid or unenforceable provision will be severed from the Airdrop Terms, but the rest of the Airdrop Terms will remain in full force and effect.

#### RISK FACTORS[​](https://docs.eigenfoundation.org/legal/airdrop-terms-and-conditions#risk-factors)

Claiming, using, transacting in, holding, and/or purchasing or selling the StakeStone token involves a high degree of risk, including unforeseen risks that may not be included below. You should consult with your legal, tax, and financial advisors and carefully consider the risks and uncertainties described below, together with all of the other information in these Airdrop Terms, before deciding whether to claim, use, transact in, hold, purchase, or sell the token. If any of the following risks were to occur, the Token or Protocol could be materially and adversely affected.

References in these risk factors to (i) the “Protocol” refers to the collection of smart contracts known as the StakeStone Protocol, (ii) the “Token” or “StakeStone” refers to the StakeStone token used on the StakeStone Protocol and (iii) “Application” refers to any ‘front-end’ or web interface that the Organization may host, including stakestone.io and any subdomain.

There is only one website for StakeStone Claims, which is the following: claims.StakeStonefoundation.org. Do not trust any other website regardless of its source or origin or any link routing you to a different website.

**Risks Relating to the Protocol**

(a) Risks Relating to the Launch of the Protocol. The StakeStone is designed to be used on the StakeStone Protocol. There can be no assurance that StakeStone or the Protocol will function as intended or as described on any website or in other communications or will be maintained and further developed according to current plans. There can be no assurance that you will be able to utilize StakeStone or the Protocol in any particular way.\
(b) Risks Relating to Smart Contracts and Programs. The Protocol is generally comprised of a number of smart contracts. Smart contracts and programs are computer codes that can be created and run by the users of the network on which such smart contract or program is based. A smart contract or program can take information as an input, process that information through the pre-determined rules and conditions defined in the computer code, and execute certain actions, such as StakeStone transactions, pursuant to such programming. The use of smart contracts and programs creates substantial risk exposures. Smart contracts are self-executing once deployed, generally without reliance on a central party, and use experimental cryptography. Smart-contract risks include the following, which may affect adoption, continued use, or functioning of the Protocol and thereby your ability to use StakeStone:

1. Flawed or Imprecise Code: Smart contract code may be imprecise or flawed. In such cases, smart contracts on StakeStone could have specifications or conditions that are implemented or executed in ways that are not expected. You may be at risk of losing all or a substantial portion of your staked digital assets through an adverse event relating to such code. Smart contracts could contain vulnerabilities or bugs that could be exploited, potentially resulting in a complete or substantial loss of your staked digital assets. Malicious actors could exploit such vulnerabilities or bugs to cause the execution of erroneous or unexpected slashing conditions or theft of your staked digital assets.
2. Lack of Remediation: If imprecise or flawed code is discovered in a deployed smart contract, it may not be susceptible to identification ex ante and remediation may be difficult or ineffective. In some cases, the only practical remediation may include deploying a new smart contract or incorporating updating mechanisms that may be disruptive, risky, complex, costly, time consuming, and/or unable to reverse adverse scenarios, including complete or substantial loss of your staked digital assets.
3. Flaws in Programming Languages: The use of programming languages in smart contracts poses risks, including vulnerabilities arising from language complexity, potential bugs and flaws in language designs or compilers, limitations in functionality or performance impacting implementation, and a lack of maturity and sustained support for certain languages impacting the reliability and security of the developed contracts. Even widely used programming languages, like Solidity, may have compiler bugs or other flaws that, if discovered and exploited, may result in substantial or total losses of your staked digital assets.
4. Irrevocable Token Transactions: The use of a distributed ledger and blockchain technology, like Ethereum, creates a public record of Token balances that is exceedingly difficult to change once it reflects a particular state. This means that if a Token transaction were executed in error or as a result of fraud or theft, such a transaction would not be practically reversible. Consequently, the Organization will be unable to replace missing or misappropriated StakeStone or seek or provide reimbursement for any such erroneous transfer, fraud, or theft. The inability to reverse transactions or seek other forms of redress for such action, error, fraud, or theft could result in the permanent loss of some or all of your Tokens. This lack of redress could cause reputational harm to, and diminish participation on, the Protocol and/or adversely affect the financial viability or performance of the Organization.
5. Lack of Control over Protocol and Upgrades: StakeStone is envisioned to be an open-source project with Protocol governance collectively controlled by a community of users (“Protocol Users,”). However, the Organization has control of certain multi-signature wallets relating to the Protocol at this time, and its control of those wallets can enable certain upgrades and transactions. Under current plans, and over time, the Organization will not have control over these wallets and the Protocol, and it will not be able to control the actions of Protocol Users. This means that although the Organization has engaged in substantial research and development with respect to the Protocol and its governance and security features, any future changes to the Protocol may need to be voluntarily adopted by Protocol Users, including, as applicable, Protocol Users participating in governance as token-holders and/or as signatories for multi-signature wallets operated by the community.\
   Because the Organization will lack control over community governance and the Protocol, under current plans, and over time, the Organization will not be able to prevent Protocol Users or others from mismanaging code, ensure that there is an adequate or timely response to emergencies or other identified risks, or adopt necessary code or governance changes. Protocol Users or others may make decisions or take actions (or fail to make decisions or take actions) in ways that adversely affect you, Protocol Users, and/or the Protocol. In addition, the Protocol may not run or function as intended, when deployed to mainnet or after upgrades or changes, and in such cases, you and the Organization may have limited recourse. Any of these could result in substantial or total losses of your staked digital assets and/or uses of StakeStone.\
   Furthermore, various technology solutions are and will be incorporated into the Protocol. Some or all of these technology solutions are relatively new and/or untested. There is significant risk to building and implementing new technologies that may have never been used or that are being used in different ways. There is no guarantee that such technologies will operate as intended or as described in any marketing or other materials distributed by the Organization or others or will continue to function according to current plans.

(c) Risks Associated with Slashing: StakeStone will enable stakers to opt-in and validate for actively validated services (“AVSs”). These stakers will have their withdrawal credentials pointed to a set of smart contracts, which subject their digital assets, such as Ether, to slashing conditions negotiated with AVSs. There is no guarantee that you or other Protocol Users will view slashing rules or conditions as precise, objective, fair, or fairly applied. There is no guarantee that any governance to mediate slashing events will be fair or impartial, or exist. The application of certain slashing rules and conditions may be challenging and/or ambiguous and lead to disagreements among stakers, other Protocol Users, and AVSs. You or other Protocol Users could have digital assets erroneously slashed, causing substantial or total losses of your staked digital assets. Your staked digital assets could be opportunistically threatened by an AVS or an operator providing validation services at your direction. Your digital assets, including StakeStone, may be partially or completely slashed despite your best efforts to validate transactions and respond to conditions as expected.

Slashing, slashing attacks, and/or any perceptions of unfair slashing could result in Protocol Users determining not to stake their digital assets on StakeStone. A sudden change in the size and constituency of the pool of digital assets supporting validation of AVSs could disrupt AVSs or StakeStone or result in disruptive changes in the prices of validation services. Any of these possibilities could diminish the use and viability of the Protocol. Any of these also could adversely impact you and adversely affect adoption of StakeStone and ultimately, your ability to use StakeStone.

(d) The Volatility and Instability of Staked Digital Assets. At this stage, the StakeStone Protocol supports only a small number of digital assets, like Ether (“ETH”) and certain liquid staking tokens (“LSTs”) representing staked ETH. The Organization is not involved in the issuance of ETH or any LST and does not vet, approve, or recommend particular LSTs or tokens for use on StakeStone. When you choose to stake ETH on Ethereum or deposit ETH or other digital assets with LSTs, you accept certain slashing and other risks that are completely exogenous to the Protocol and beyond the Organization’s control.

Protocol Users may seek to support new types of digital assets on the Protocol. These may include new types of LSTs not presently supported by the Protocol. It is also possible that validated services on StakeStone could be supported by any digital asset acceptable to AVSs. These assets may have widely varying characteristics and quality and these could change and deteriorate over time. Any exogenous factor that reduces the value, useability, or liquidity of a staked digital asset could affect the overall number and value of digital assets supporting AVSs, triggering potential expansions and contractions of digital assets available to support validation services. The Organization will not be able to control these possibilities or events, and these events may be difficult to predict and mitigate. Any of these could adversely affect economic considerations for providing validation services, adoption of StakeStone, and/or ultimately, your ability to use StakeStone.

(e) Insufficient Interest in the Protocol and Token. The Protocol relies on active engagement by users to function. The Organization makes no assurance that the Protocol will generate enough interest and user engagement to be viable or continue to be viable. It is not possible at this time to evaluate whether sufficient users will participate in the Protocol and whether those users will sustainably and sufficiently engage with and use the Protocol for the Protocol to function as intended. Protocol Users could mismanage, misuse, or misappropriate aspects of the Protocol or StakeStone in a manner that is detrimental to you, the Protocol, and the broader community of users. This may be adverse to your ability to use StakeStone.

(f) Risks of Adverse Contagion from Ethereum Events. The Protocol is comprised of a set of smart contracts deployed on Ethereum, and the Protocol has been designed in the spirit of remaining closely aligned with the Ethereum community’s mission and roadmap. This presents the following risks, among others:

1. Discovery of EVM Flaws. An Ethereum Virtual Machine (“EVM”) bug discovered and exploited by malicious actors could present risks to the integrity and security of the Protocol because its smart contracts are deployed on Ethereum. EVM compromises could impair expected execution of the Protocol, resulting in security vulnerabilities, data corruption that changes or obscures true data states, disruptions to operations such as withdrawals, and ultimately, substantial or total losses of digital assets, fees, or support or adoption of Ethereum-based projects, including AVSs relying on StakeStone validation services. This could diminish the use of StakeStone and result in substantial or total losses of digital assets and confidence across the crypto markets more generally.
2. Ethereum Hard Fork. In the event of a hard fork on Ethereum, changes could be made to the Ethereum protocol that could make the Protocol’s smart contracts incompatible, dysfunctional, uneconomic, or more costly, which could impair the execution and interaction of smart contracts essential to the operation of StakeStone. Such changes also could adversely affect the ability or incentives of Ethereum stakers or AVSs to use the Protocol. A hard fork on Ethereum could necessitate significant changes to the Protocol that, in turn, change the economics or technical processes involved in validating AVSs and maintaining staker and developer interest. Certain types of changes in consensus rules or technical implementations could present significant or even existential risks to the Protocol, such as those that could make it difficult, costly, or slashable to support a shared security model under the Protocol. Significant resources and time could be required for the Protocol to remain compatible with one or more forks of Ethereum or consensus rule changes. Such resources or time may be unavailable or uneconomic to provide and cannot be guaranteed to ensure continued operation of the Protocol.
3. Insufficient Quantum Resistance. Quantum computers, if sufficiently powerful and available for use, potentially could be used to break the cryptographic algorithms used by Ethereum, the Protocol, and other platforms. This could make it possible to derive private keys from public keys, opening the door to a variety of storage and other attacks that could harm Ethereum itself, holders of ETH, and Protocol Users building or transacting on the Protocol. This, in turn, could adversely affect adoption of StakeStone and ultimately, your ability to use StakeStone.
4. Slashing Events on Ethereum. If a Protocol User is slashed on an initially staked ETH position on Ethereum, communication latencies and expected Protocol limitations may prevent immediate adjustment of the economic incentives associated with slashing on the Protocol. This, in turn, could potentially incentivize negligent, harmful, or malicious validation activities and failures. Loss events or disruptions to AVSs arising from changes in such incentives could adversely affect adoption of StakeStone and ultimately, your ability to use StakeStone.

(g) Risks Associated with the Concentration of Staked Digital Assets. If staked digital assets on StakeStone become too concentrated, there could be significant governance and economic risks to the Protocol. Significant concentration may result in certain stakers having significant governance powers and enable such stakers to exert influence or control over economic and technical interactions between stakers, AVSs, and operators. This concentration could arise from unaffiliated parties developing their own LSTs or liquid restaking tokens (“LRTs”) designed to facilitate indirect access to AVSs and provide a more liquid alternative to staking directly via the Protocol. Such concentrated governance power could be exercised to benefit LST or LRT organizers to the detriment of the broader StakeStone community. Under current plans, the Organization will have no way to prevent concentration of staked assets or implementation of initiatives within the Protocol’s governance that may result in increased concentration of staked digital assets. The withdrawal of a dominant issuer of an LST or LRT, including due to poor risk management, a de-pegging event, or fraud at the LRT, could destabilize the Protocol and result in substantial or total losses of the use of StakeStone.

(h) Multiple Other Significant Risks. It is possible that, due to any number of reasons, including but not limited to, lack of interest from users or partners, inability to attract sustained third-party or community contributors to the Protocol, an unfavorable fluctuation in the value of digital and fiat assets and currencies, decrease in the utility of StakeStone, failure to generate commercial relationships, intellectual property ownership and other challenges, and macroeconomic and crypto-market-specific factors, the Protocol may no longer be viable to operate and it may be deprecated or cease to have any functionality, users, or viability.\ <br>

**Risks Relating to the StakeStone Token**

(a) Risks Relating to the StakeStone in Particular. Significant market and economic factors may adversely affect your ability to use StakeStone:

1. No Market for the Token. There is no public market for the StakeStone, and the Organization does not control the development of such a market. A public market may not develop or be sustainable, and you may not be able to sell your StakeStone. Furthermore, the Organization cannot control how StakeStone holders or third-party exchanges or platforms may support the StakeStone, if at all. Even if a public market for the StakeStone develops, such a market may be relatively new and subject to little or no regulatory oversight, making it more susceptible to fraud or manipulation.
2. Extreme Illiquidity. There will be significant restrictions on the transferability of your StakeStone. The transfer restrictions on your StakeStone will remain in place for a significant period of time. Even if a public market does eventually exist, you may not be able to freely sell or transfer your StakeStone. If you can freely sell your tokens in a public market after some period of time, the depth and volume in that market may be insufficient for you to sell without substantial price concessions.
3. Inflation. Due to the nature and operation of blockchain protocols, the total amount of circulating StakeStone could increase through the adoption of a new patch or upgrade of the source code. An increase in the quantity of StakeStone, or inflation, could adversely impact you as a holder of StakeStone.
4. Adverse Activities in Secondary Markets. Secondary market activities that are beyond the control of the Organization could develop that are adverse to your ability to use StakeStone. Even with significant transfer restrictions intended to support long-term alignment with the StakeStone community, significant concentrations in StakeStone positions are present and may continue to be present among a relatively small group of StakeStone holders, or worsen, exposing you to significant risks of volatility, herd trading, “dumping,” or other correlated secondary market activities. These risks will be considerable following expiration of the one-year lock-up period applicable to certain StakeStone holders, including Organization service providers and recipients of StakeStone allocations from StakeStone, a core contributor to the Protocol. In addition, Protocol Users may determine to approve grants, allocations, and/or inflationary mints of StakeStone, all of which may be fully or partially outside of the Organization’s control and could incentivize harmful short-term trading activities or otherwise adversely affect you.
5. Experimental Features and Uses. StakeStone may be upgradeable to have experimental features and uses. Future features and uses may prove not to be valuable, usable, or viable, and contributors may fail to adequately research and develop any such upgrades. Under current plans, and over time, the Organization may not have the ability to effectuate upgrades to implement new features and use cases. Such upgrades may not be approved in Protocol governance or may be adopted with security flaws or with unexpected or harmful changes that are adverse to your ability to use your StakeStone.

(b) Risks Relating to Governance. StakeStone were minted using an upgradeable smart contract. The Organization has control of certain multi-signature wallets that can enable certain upgrades and transactions. However, any upgrades in the future may involve code changes that, under current plans, and over time, will be controlled by Protocol Users. Thus, the Organization may not have control over smart-contract upgrades or administrative actions necessary to execute those upgrades, under current plans, and over time, nor will it be able to control the decisions and actions of Protocol Users. This means that any future upgrades to the StakeStone smart contract will need to be voluntarily adopted by Protocol Users, including, as applicable, Protocol Users participating in governance as token-holders and/or as signatories for multi-signature wallets operated by the community.

Because the Organization will lack control over community governance, under current plans, and over time, it will have limited means to prevent Protocol Users from mismanaging smart-contract code, ensure that there is an adequate or timely response to emergencies or other identified risks, or adopt necessary code or governance changes. Protocol Users may make decisions or take actions (or fail to make decisions or take actions) in ways that adversely affect you, others, and/or the smart contract, including by limiting transfers of StakeStone or removing transfer restrictions, authorizing inflationary minting of StakeStone, or misappropriating a portion of the StakeStone supply.

Furthermore, StakeStone may be staked to support certain AVSs that are not owned or controlled by the Organization. In these cases, StakeStone may interact with compatible ERC-20 contracts that enable StakeStone holders to initiate certain slashing events intended to deter and punish malicious actions. In connection with any such slashing event, StakeStone holders may take actions that adversely affect StakeStone or your ability to use StakeStone.\ <br>

**Risks Related to Legal and Regulatory**

(a) Risks of New & Evolving Laws and Regulations: There is significant risk surrounding the ongoing development of regulatory frameworks governing blockchain technology all over the world, including in the United States, and as the blockchain, crypto, and web3 industry continues to grow, the Organization expects regulatory scrutiny to increase across jurisdictions. The Organization or the Protocol or StakeStone may be found to be subject to certain laws or regulatory regimes that could adversely impact you, the Protocol, or StakeStone. Additionally, laws or interpretations may change and the Organization or the Protocol or StakeStone may be subject to new or changed laws or regulations in the future. Any restrictive or prohibitive legislation or regulation on blockchains or digital assets could impair the adoption of the Protocol and/or the use of StakeStone and adversely affect market sentiment surrounding the Protocol and/or StakeStone.

To the extent licenses, permits, or other authorizations are required in one or more jurisdictions in which the Protocol or any Application is deemed to operate, there is no guarantee that the Organization or another party will be able to secure such licenses, permits, or authorizations in order for the Protocol or any Application to continue to operate. Significant changes may need to be made to the Protocol to comply with any licensing and/or registration requirements (or any other legal or regulatory requirements) in order to avoid violating applicable laws or regulations or because of the cost of such compliance. Uncertainty in how the legal and regulatory environment will develop could negatively impact the development, growth, and utilization of the Protocol and therefore the uses of StakeStone.

(b) Risks of StakeStone or StakeStone Transactions Being Deemed Securities. The U.S. Securities and Exchange Commission (“SEC”) and its staff have taken the position that certain tokens and/or certain transactions involving tokens fall within the definition of a “security” under the U.S. federal securities laws. In addition, in recent months, the SEC has brought enforcement actions against centralized crypto exchanges offering staking arrangements, often called staking-as-a-service, that it contends constitute securities. The legal test for determining whether any given token or transaction is a security is a highly complex, fact-driven analysis that evolves with U.S. case law and developments over time, and the outcome(s) or conclusion(s) of any such legal analysis may be uncertain or evolve in ways that are difficult to predict. The SEC generally does not provide advance guidance on or confirmation of whether any particular token or transaction is or may be a security. Furthermore, the SEC’s views in this area have evolved over time and it is difficult to predict the direction or timing of any continuing evolution. It is also possible that legislative or judicial developments or a change in the governing administration or the appointment of new SEC commissioners could substantially impact the views of the SEC and its staff. Further, certain tokens or transactions may be deemed to be other types of regulated financial instruments or transactions in the U.S.; or securities or other regulated financial instruments or transactions in other jurisdictions. As a result, certain tokens or transactions may be deemed to be “securities” or other regulated financial instruments or transactions under the laws of some jurisdictions but not others. Various foreign jurisdictions may, in the future, adopt additional laws, regulations, or directives that affect the characterization of certain tokens or transactions as “securities” or other regulated financial instruments. The classification of a token or transaction as a security or regulated financial instrument under applicable law has wide-ranging implications for the regulatory obligations that could be imparted on the Organization, Protocol, Protocol Users, or holders of StakeStone, including obligations that could make the Protocol not viable to continue to operate or negatively impact the development, growth, and utilization of the Protocol and liquidity and market sentiment around StakeStone.

(c) Risk of Third-Party Illegal Activity. The Protocol and Token may be exploited to facilitate illegal activity including fraud, money laundering, gambling, tax evasion, sanctions evasion, and scams. If any third party uses the Protocol or StakeStone to further such illegal activities, that and the legal and regulatory consequences of those activities could negatively impact the development, growth, and utilization of the Protocol. While we do not control the activities of the Protocol’s users, the use of the Protocol for illegal or improper purposes could subject us, the Protocol, or StakeStone holders to claims, individual and class action lawsuits, and government and regulatory investigations, prosecutions, enforcement actions, inquiries, or requests that could result in liability and reputational harm for us, the Protocol, and/or the Token holders.

Certain activities that may be legal in one jurisdiction may be illegal in another jurisdiction, and certain activities that are at one time legal may in the future be deemed illegal in the same jurisdiction. In the event that a Protocol User is found responsible for intentionally or inadvertently violating the laws in any jurisdiction, the Organization, Protocol and/or you and other Token holders may be subject to governmental inquiries, enforcement actions, prosecution, or held secondarily liable for aiding or facilitating such activities in researching and developing, or deploying, software that enabled such activities, being a platform on which such activities occurred, contributing to governance that authorized such activities, or being a member of a decentralized autonomous organization or other group that otherwise has liability with respect to such activities.

(d) Risk of Sanctions Violations. The Organization, the Protocol, or StakeStone holders could be deemed to be violating or facilitating the violation of applicable economic and trade sanctions and export control laws and regulations, such as those administered and enforced by the U.S. Department of the Treasury’s OFAC, the U.S. Department of State, the U.S. Department of Commerce, the UN Security Council, and other relevant authorities. Such laws and regulations prohibit or restrict certain operations, investments, services, and sales activities, including dealings with certain countries or territories (e.g., sanctioned countries), and governments, and persons (including sanctioned entities). Although the Organization does not enter into contracts or agreements with sanctioned entities or persons located in sanctioned countries, it may not be able to entirely prevent such persons from seeking to interact with the Protocol, StakeStone, and/or StakeStone holders, including by circumventing the Organization’s controls. Abuses of the Protocol and failures or alleged failures to comply with such laws and regulations may expose the Protocol, Protocol Users, the Organization, and/or StakeStone holders to reputational harm as well as significant penalties, including criminal fines, imprisonment, civil fines, disgorgement of profits, injunctions and debarment from government contracts, as well as other remedial measures, and could negatively impact the development, growth, and utilization of the Protocol and market sentiment around StakeStone.

(e) Risk of Entering into a General Partnership. It could be alleged that by holding StakeStone or using StakeStone to vote on governance proposals in relation to the Protocol, the holders of StakeStone have entered into a general partnership, unincorporated association, or some other form of legal entity or association with other StakeStone holders or a group of such holders. At least one court in the United States has found that certain holders of a governance token constituted an unincorporated association. If this were to be found or alleged with respect to StakeStone, holders of StakeStone could be held responsible for the actions of the other members of the unincorporated association or general partnership, or the Protocol itself, and subject to up to unlimited liability with respect to those actions. Additionally, such an allegation could negatively impact market sentiment around the Protocol or the StakeStone and discourage participation in the Protocol or utilization of StakeStone.

(f) Risks Associated with the Tax Treatment of Digital Assets. Due to the new and evolving nature of digital assets and the absence of comprehensive legal guidance with respect to digital asset transactions, the taxation of digital assets is uncertain, and it is unclear what guidance may be issued in the future on the treatment of digital asset transactions for tax purposes. Guidance under, or changes in, the tax laws applicable to of digital assets, including StakeStone, or the Organization and/or its activities and transactions, either directly or through subsidiaries, could adversely impact the value of StakeStone or your ability to use or engage in certain types of transactions with StakeStone. The Organization or its subsidiaries may also have tax reporting obligations in various jurisdictions with respect to Airdrop StakeStone. You should consult a tax advisor with respect to the tax treatment of Airdrop StakeStone in your jurisdiction.

\
**Operational Risks**

(a) Risks of Competition. The Protocol and the StakeStone compete against a variety of existing products and platforms as well as likely new entrants into the market. Some of these current or future competing protocols and products may be subject to different regulatory regimes than the Organization, the Protocol, or StakeStone that may facilitate broader or faster adoption such that they can outcompete the Protocol. Alternatively, other competitors may exercise different amounts of control over the protocol they design that allow for faster or broader adoption. Additionally, competitors may develop more successful protocols, applications, or tokens for a variety of other reasons, including but not limited to designing a more friendly user experience, offering more compelling incentives, attracting more developers and users to the protocol, creating a more sustainable token economic design, or taking a more permissive view of applicable law.

(b) Risks of Security Weaknesses or Attacks. Cyberattacks and security breaches of an Application or the Protocol or StakeStone, or those impacting the Protocol’s users or third parties such as decentralized applications or crypto wallets that interact with the Protocol or StakeStone, could cause you to lose StakeStone, or adversely impact the Protocol or StakeStone. The Protocol could be vulnerable in a variety of ways, including but not limited to, malware attacks, denial of service attacks, consensus-based attacks, Sybil attacks, smurfing and spoofing, governance attacks, exploitable code, or any number of other currently known or novel methods of exploit. Additionally, as mentioned above, upgrades or changes to the Protocol or StakeStone, which may be proposed, coded, and/or implemented by parties other than the Organization, could introduce new vulnerabilities to the Protocol or StakeStone or otherwise have unintended or malicious adverse effects on the Protocol and/or StakeStone. The Protocol and smart contracts generally execute automatically when certain conditions are met and typically cannot be stopped or reversed, so any vulnerabilities that may arise can have significant adverse effects to the Protocol, StakeStone, and holders of StakeStone.

Further, any actual or perceived breach or cybersecurity attack directed at crypto companies or blockchain networks, whether or not the Protocol is directly impacted, could lead to a general loss of user confidence in the crypto-economy or in the use of blockchain technology to conduct transactions, which could negatively impact the Protocol, including the market perception of the effectiveness of security measures and technology infrastructure. Digital assets are generally controllable only by the possessor of a unique public and private key pair. To the extent your private key for your wallet is lost, destroyed, or otherwise compromised and no backup of the private key is accessible, you will be unable to access the tokens held in such wallet.

Any StakeStone that are custodied, managed, escrowed, or supported by a third party, like Cobo, a custodian providing certain services to the Organization with respect to the StakeStone, may be subject to a security breach, cyberattack, or other malicious activity, or otherwise lost or stolen. Such an event could severely impact you and your StakeStone holdings and your ability to use StakeStone.

(c) Risk of Decentralized Operations. Coordinating operations and implementation of feature updates, new product launches, or community initiatives amongst a distributed community can result in inefficiencies and delays. Such inefficiencies and delays could create stagnation around new developments and improvements to the Protocol and could allow more centralized competitors to act more efficiently and outcompete the Protocol, resulting in decreased usage or negative sentiment around the Protocol and StakeStone.

Conversely, the Organization’s role as a contributor to research and development involving the Protocol and StakeStone presents certain risks, given the lack of operating history of the Organization, the relative inexperience of certain service providers, and the novel nature of the Protocol and potential use cases for StakeStone.

In addition, there will be certain multi-signature wallets that have certain transactional authorities and controls related to the Protocol and StakeStone, and these may include, but are not limited to, the ability to pause certain functionality of the Protocol, reverse or pause slashing, implement or influence upgrades, and implement certain other controls or changes to functionality. At this time, certain of these multi-signature wallets may be controlled by us or certain contributors or Protocol Users engaged by us, and certain other wallets may be controlled partially or entirely by committee members that are unaffiliated third parties over which the Organization has no or limited control. The Organization intends, under current plans, and over time, to turn all multi-signature wallets over to the community, to parties that are independent of the Organization. Those parties may choose to act in ways that could cause risk or damage to the Protocol or the uses of StakeStone.

(d) Unanticipated Risks. Cryptographic tokens and blockchain-based protocols are new and untested technologies. StakeStone, as well as the Protocol and its design concepts, smart-contract mechanisms, algorithms, codes, and other technical details and parameters may be updated and changed. In addition to these risks, there may be other risks associated with your claiming, using, buying, transacting in, and/or holding StakeStone, including those which we cannot anticipate or have not specifically enumerated here. Such risks may further materialize as unanticipated variations or combinations of the risks discussed. Further, new risks may be created as the Protocol and StakeStone are developed (including by parties other than us) or third parties integrate StakeStone or the Protocol into their products. No person, including the Organization has an ability or obligation to keep Participants informed of details related to development of the Protocol or StakeStone. Lack of available information may create risk for you.

(e) Fraudulent Websites. Some users have been targeted and/or have reported fraudulent websites, emails, text messages, and social media handles, often including embedded or published links, impersonating projects, persons, entities, or service providers of or associated with the Organization for the purpose of defrauding users, stealing their digital assets, or otherwise unlawfully profiting from such activities. These fraud and theft risks may materialize in connection with StakeStone Claims, and you should remain extremely cautious about websites, emails, text messages, and social media handles, as well as any embedded or published links, that direct you to websites or to take actions, especially connecting to your Wallet.

There is only one website for StakeStone Claims, which is the following: claims.stakestone.io

\
Do not trust any other website regardless of its source or origin or any link routing you to a different website.

How to Contact Us. You may contact us regarding the Services or these Terms by e-mail at <contact@stakestone.io>.

<br>


# Privacy Policy

Last Revised on September 19, 2024

This Privacy Policy (“Policy”) for StakeStone, a Cayman Islands company, and its subsidiaries (“Organization”, “we”, “our”, or “us”) describes the basis on which we will process personal data we collect from users of the Organization’s website, stakestone.io, including any of its subdomains (“Website”), and any tools, services, features, and functionalities available through the Website (collectively, the “Services”), in accordance with applicable law. For purposes of applicable data protection laws, the Organization is the controller. For the purposes of this Policy, “you” and “your” refers to you as the user of the Services.

Please read this Policy carefully so that you understand your rights in relation to your personal data and how we will collect, use, and process your personal data. If you do not agree to this Policy, please do not use, access, connect to, interact with, or download any of the Services or otherwise provide your information to us.

#### PERSONAL DATA WE COLLECT ABOUT YOU, WHY WE PROCESS IT, AND THE LEGAL BASIS FOR PROCESSING

When you access, use, connect to, or interact with the Services, we may collect certain categories of information about you, including personal data, from a variety of sources.

Information you provide to us:

Personal data may include (i) names; (ii) addresses; (iii) telephone numbers; (iv) email addresses; (v) government-issued identification numbers; (vi) user passwords or PINs; (vii) user identification and account access credentials, passwords, PINs, and security question answers; (viii) financial account numbers; (ix) any internet-protocol address (“IP Address”) and/or any Ethereum or similar digital-asset, smart-contract, or protocol address (“Wallet”) information, associations, and/or identifiers; and (x) geolocation data.

In addition, personal data may include your social media handle and related information, transaction data or history (such as your blockchain transaction history and other information associated with a linked address or Wallet), certain information needed to transfer or allocate tokens, profile data (such as your profile name and avatar), marketing data (such as preferences for receiving marketing communications and related details), token holdings, and any other information collected through Services. When you contact us, including by email provided in this Policy or elsewhere on the Website, or through emails that you may have received through other means, we will collect the content of the communications we have with you and any personal data contained within.

We process this information to perform our contract with you, such as to provide you with our Services and content. We obtain your consent to process your personal data to sign you up for alerts and if you opt into marketing, to communicate with you about our products, features, services, marketing, events, and other news and information we think will be of interest to you. In order to be responsive to you, to provide effective services to you, and to maintain our business relationship, we may also use this information to send you announcements in relation to security, privacy, or administrative related communications (which are not marketing oriented, and so we do not rely on consent, so you may not opt-out) and to communicate with you and provide responses to your requests and other communications.

Information we collect automatically:

When you visit our Website or access, use, connect to, or interact with the Services, our servers temporarily save each access in a log file. The following data may be collected: (i) the IP Address of the requesting computer or device; (ii) the name of your internet access provider (usually your internet access provider); (iii) the date and time of access; (iv) the name and URL of the retrieved file; (v) the page and address of the website from which you were redirected to the website and, if applicable, the search term used; (vi) the country from which the website is accessed; (vii) the operating system of your computer and the browser you are using (provider, version, and language); and (viii) the transmission protocol used (e.g., HTTP/1.1).

The processing of this data is carried out for the purpose of enabling your access to, use of, connection to, and interaction with the Services, including (i) to facilitate your connection to the Website, (ii) to identify if you are likely to be a Prohibited Person, as defined in our general Terms of Service, available at stakestone.io, or if you are subject to any prohibitions with respect to the Services and other terms of services; and/or (iii) to verify your identity, identifying information, certain facts with respect to your identity or identifying information, and location to determine eligibility for certain Services, in each case with respect to any of (i), (ii), and/or (iii) in order for us to perform our contract with you and in our legitimate interests to provide effective Services to you.

We also process this data in our legitimate interests to provide effective Services to you by processing the data to assist system security and stability for provision of the Services, to conduct troubleshooting, data analytics, testing, and research, and to enable optimization and internal statistical analysis with respect to the Services, as well as to maintain the safety and security of our users, the Website, our Services, and business and to improve and develop our Services and Website.

Finally, the Organization may use cookies, web beacons/clear gifs, geolocation and tracking technologies, and other applications when you visit the Website, including technologies collecting certain information about your access to, use of, connection to, or interaction with the Services (“Usage Data”) that may be integrated with third-party service providers.

With your consent, we may use any data collected, including Usage Data, to tailor features and content to you and to ensure content is presented in the most effective manner for you and your device and to run analytics and better understand your user experience with respect to the Services and, if you have opted into marketing, for marketing purposes. For further information, please refer to sections “Cookies” and “Tracking Tools”.

We may also use your information to provide the Services and perform our contract with you. In our legitimate interests to provide effective services to you, we may also use this data to create aggregated, anonymized, or de-identified data.

In addition to the foregoing, we may use any of your information to comply with any applicable legal obligations, to enforce any applicable terms of service, and to protect or defend the Services, our rights, and the rights of our users or others.<br>


# Tokenomics

### Token Overview <a href="#id-3116" id="id-3116"></a>

| **Token Name**                                  | STO                                        |
| ----------------------------------------------- | ------------------------------------------ |
| **Token Type**                                  | ERC-20                                     |
| **Initial Circ. Supply When Listed on Binance** | 225,333,333                                |
| **Maximum Token Supply**                        | 1,000,000,000                              |
| **Total Token Supply**                          | 1,000,000,000                              |
| STO (BNB Chain)                                 | 0xdAf1695c41327b61B9b9965Ac6A5843A3198cf07 |
| STO (ETH L1)                                    | 0x1D88713b483A8E45cfF0e5CD7c2e15E5Fab4534d |

### Allocation Breakdown <a href="#allocation-breakdown" id="allocation-breakdown"></a>

| Community                   | 17.87% |
| --------------------------- | ------ |
| Ecosystem and Treasury      | 4%     |
| Team                        | 15%    |
| Foundation                  | 18.65% |
| Airdrop & Future Incentives | 7.85%  |
| Marketing & Partnership     | 9.13%  |
| Liquidity                   | 6%     |
| Investor                    | 21.5%  |

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FoWIA4I20Yx0R2wn5Cn7l%2Fimage.png?alt=media&amp;token=ea8c3fc6-0925-4095-b4eb-7711e24fde53" alt=""><figcaption></figcaption></figure>

### Release Schedule

<figure><img src="https://3335806686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCQc6hVwS1NTaUDN4XLdQ%2Fuploads%2FFo4vebnehTPbFqftYzI3%2Fimage.png?alt=media&amp;token=c52fb665-9fa1-40c5-b2bc-38e3bc4703b3" alt=""><figcaption></figcaption></figure>

### Current Holding Addresses

| **Investors**          | 0x175d83B63114303C575059A26bd8B5f557475F6F |
| ---------------------- | ------------------------------------------ |
| Foundation             | 0x63b89dA1Ac50019893c9835fEcA6b1e8BFE6d307 |
| Team                   | 0x620e7F2Fe612d9F06748D2d8D743cdCbf35120dA |
| Ecosystem and Treasury | 0xA8F252E94b8Cc356fb92db400E08d3BdbFC62BE9 |
| Community              | 0xed8C7145a67d0226eE11FDA69F11221Fb5692808 |
| Others                 | 0x7b61491034A97183Ff9385bEe07a5C881faebE78 |

The current wallets are strictly managed by the team using multi-signatures and cold wallets. The new vesting contract will be set up within half a year after TGE (before investor vesting starts) and pass audits before deployment. By then, unvested tokens will be secured by multisig, hardware wallets and vesting smart contract collectively. Detailed information will be updated once new deployment is completed.


# STONEUSD Custodian Attestation

#### Ceffu

{% file src="/files/AiTYGe7GOOaXW0Zj8rp5" %}

{% file src="/files/F5hMbkIvYWmpEJLVHnMr" %}

{% file src="/files/dfEtTB5HaydpQsJtBtF2" %}


