The trading rules govern and ensure a safe and fair trading environment.
1.1 Account has the meaning given thereto in the User Agreement.
1.2 AFM means the Dutch Authority for Financial Markets (Autoriteit Financiƫle Markten).
1.3 Algorithmic Trading means the use of computer algorithms that automatically determine individual parameters of orders resulting in investment and/or execution decisions based on predefined criteria and strategies with limited or no human intervention.
1.4 API means Application Programming Interface.
1.5 API Credentials means the API key(s) with corresponding secrets.
1.6 API Trading Bot means an automated software application that interacts with the Bitvavo Trading Platform via API to execute trades based on predefined algorithms or strategies.
1.7 App has the meaning given thereto in the User Agreement.
1.8 Auction means the process as described in Section 6.8 of these Trading Rules.
1.9 Broker means a Participant as referred to in Section 4.6 of these Trading Rules.
1.10 Bitvavo means Bitvavo B.V.
1.11 Bitvavo Custody means Bitvavo Custody B.V.
1.12 Bitvavo E-Token has the meaning given thereto in the User Agreement.
1.13 Bitvavo Trading Platform means the Digital Asset trading platform operated by Bitvavo.
1.14 Cancel Only means the status of the Bitvavo Trading Platform whereby users are restricted to cancelling existing orders, either for a specific Digital Asset or on the entire trading platform.
1.15 CASP means a crypto-asset service provider as defined in MiCA.
1.16 CLOB means central limit order book.
1.17 Corporate Participant is a Participant as referred to Section 4.4 of these Trading Rules.
1.18 Digital Asset has the meaning given thereto in the User Agreement.
1.19 EBA means European Banking Authority.
1.20 EEA means European Economic Area.
1.21 Fee means any charge or cost imposed by Bitvavo on an Issuer or a Participant for the execution of transactions, provision of Services, or maintenance of an Account, admission to trading or otherwise.
1.22 Funds has the meaning given thereto in the User Agreement.
1.23 Halted means the status of the Bitvavo Trading Platform whereby there is a temporary suspension of trading activity, either for a specific Digital Asset or on the entire trading platform.
1.24 High Frequency Trading means an infrastructure intended to minimise network and other types of latencies that enable Algorithmic Trading at high speed.
1.25 Issuer means issuer as defined in MiCA.
1.26 Limit Order means an Order as described in Section 6.1(a)(ii) of these Trading Rules.
1.27 Market Maker means a Participant as referred to in Section 4.5 of these Trading Rules.
1.28 Market Order means an Order as described in Section 6.1(a)(i) of these Trading Rules.
1.29 Market Specification means the document that describes the attributes of a specific Digital Asset as defined in Section 5.7 of these Trading Rules.
1.30 MiCA means Regulation (EU) 2023/1114 on markets in crypto-assets, as amended or supplemented from time to time.
1.31 Order means an instruction to buy or sell Digital Assets on the Bitvavo Trading Platform.
1.32 Order Book means a digital ledger maintained by Bitvavo that records all buy and sell orders for a specific cryptocurrency pair.
1.33 Participant means any natural person or legal entity that engages in trading activities on the Bitvavo Trading Platform.
1.34 Price GuaranteeĀ Service means the price guarantee service, which is a service provided by Bitvavo that protects the Participant against price fluctuations in a specific Digital Asset for a pre-defined period of time.
1.35 Reference Price has the meaning given thereto in Section 6.3 (f) of these Trading Rules.Ā Ā
1.36 RfQ means Request for Quote.
1.37 RfQ Segment means the segment of the Bitvavo Trading Platform where Orders of the Participants opted in for Price Guarantee Services are routed pursuant to these Trading Rules.Ā
1.38 Retail Participant is a Participant as referred to in Section 4.3 of these Trading Rules.
1.39 Services has the meaning given thereto in the User Agreement.
1.40 Stop Loss Order means an Order as described in Section 6.1(b)(i) of these Trading Rules.
1.41 Stop Loss Limit Order means an Order as described in Section 6.1(b)(ii) of these Trading Rules.
1.42 Take Profit Order means an Order as described in Section 6.1(b)(iii) of these Trading Rules.
1.43 Take Profit Limit Order means an Order as described in Section 6.1(b)(iv) of these Trading Rules.
1.44 Tick Size means the minimum price increment between two valid order prices for a market. Orders must be priced in multiples of the configured tick size.Ā
1.45 Trading Rules means these trading rules.
1.46 US Person means a United States citizen or resident individual, a partnership or corporation organized in the United States or under the laws of the United States or any State thereof, a trust if (i) a court within the United States would have authority under applicable law to render orders or judgments concerning substantially all issues regarding administration of the trust, and (ii) one or more U.S. persons have the authority to control all substantial decisions of the trust, or an estate of a decedent that is a citizen or resident of the United States.
1.47 User Agreement means the contractual agreement between the Participant, Bitvavo, Bitvavo Custody B.V., and Stichting Bitvavo Payments, which defines and governs the provision of the Services by the relevant entities and the use of the Services by Participants.
1.48 Website has the meaning given thereto in the User Agreement.
2.1 The Bitvavo Trading Platform
Bitvavo operates a trading platform which manages several trading systems such as the CLOB segment and the RfQ segment, where Digital Assets can be purchased or sold, resulting in the exchange of Funds for Digital Assets and Digital Assets for other Digital Assets (āthe Bitvavo Trading Platformā).
2.2 Licence
Bitvavo is licensed by the AFM under the registration number 41000010,Ā as a CASP under MiCA and is, among others, permitted to provide the Digital Asset service āoperation of a trading platform for Digital Assetsā. This service may be madeĀ available by Bitvavo in all EEA jurisdictions.
Bitvavo reserves the right to not make the Bitvavo Trading Platform available in all markets or jurisdictions where it is authorized or permitted to provide its Services, and may restrict or prohibit the use of the Bitvavo Trading Platform by residents of certain jurisdictions.
These trading rules ensure compliance with Article 76 MiCA and promote fair, efficient and transparent trading on the Bitvavo Trading Platform.
3.1 Requirements for (Issuers of) Digital Assets seeking admission to trading at Bitvavo
(a) Bitvavo has implemented a Digital Asset admission process based on which Bitvavo determines whether a new Digital Asset can be admitted to trading on the Bitvavo Trading Platform. Bitvavo may in its sole discretion determine whether or not a Digital Asset can be admitted to trading on the Bitvavo Trading Platform.
(b) Each Digital Asset to be admitted to trading on the Bitvavo Trading Platform should meet and continue to meet requirements on its business case, feasibility, compliance, legal, risk and suitability requirements as set by Bitvavo from time to time.
3.2 Application procedure for admission to trading at Bitvavo
The application procedure will be carried out in accordance with Bitvavoās policies and procedures. In summary, Bitvavo considers the following criteria:Ā
(a) a business case assessment (including market viability and economic and strategic fundamentals) and pre-scan (for the feasibility and compliance assessment);
(b) a feasibility assessment (including custody, liquidity and blockchain integration);
(c) a compliance, legal and risk assessment (compliance with applicable laws, KYC, customer due diligence assessments proportionate to the risk profile of the applicant, audit and privacy and the risks associated with the Digital Asset);
(d) a suitability assessment (asset value, security, technology and additional risk and compliance requirements); andĀ
(e) admission to go-live preparation (date, technological preparation, liquidity and inventory and communication).Ā
3.3 Conditions for Digital Assets to remain admitted to trading
(a) Liquidity thresholds
To remain eligible for trading, each Digital Asset that is admitted to trading on the Bitvavo Trading Platform must consistently achieve a daily average transaction volume that meets or exceeds the threshold periodically set by Bitvavo.
(b) Disclosure requirements
To remain eligible for trading, Issuers of Digital Assets must at minimum disclose the following information on their website:
(i) a Digital Asset whitepaper in compliance with the requirements in MiCA, if applicable; and
(ii) whenever there is a significant new factor, material mistake or material inaccuracy that can affect the assessment of the Digital Assets, the modified Digital Asset whitepaper, including the reasons for such modification, in accordance with MiCA, if applicable.
3.4 Ongoing monitoring of Issuers and Digital Assets
(a) To ensure continued credibility, security and efficiency of its markets and the Digital Assets that are admitted to trading and their compliance with this Section 3 of the Trading Rules, Bitvavo continuously monitors applicable risk factors that would possibly lead to a trading suspension or a delisting of any admitted Digital Assets. To perform this ongoing monitoring, Bitvavo leverages automated alerts and tooling that may prompt re-evaluations of Digital Assets admitted to trading, taking into account developments in the Digital Assets market, including regulatory changes, technological issues or changes, market dynamics, liquidity and concentration of the Digital Assets.
(b) With regard to liquidity, Bitvavo assesses whether the liquidity provided by market makers to the Order Book is appropriately aligned with the Order volumes in the Order Book. Bitvavo also assesses the trading activity in the relevant Digital Asset on other Digital Asset trading platforms.
3.5 Digital Assets Not Admitted to Trading at the Bitvavo Trading Platform
A Digital Asset is not admitted to trading on the Bitvavo Trading Platform if:
(a) it does not pass the application procedure as referred to in Section 3.2 of these Trading Rules;
(b) no corresponding Digital Asset white paper has been published in the cases required by MiCA; or
(c) it has an inbuilt anonymization function, unless the holders and transaction history can be identified by Bitvavo.
4.1 Participant criteria
A person can be a Participant of the Bitvavo Trading Platform if:
(a) the person has created an Account as set out in the User Agreement;
(b) the person has accepted the User Agreement and these Trading Rules.
(c) the person complies with mandatory regulatory obligations related to Market Abuse prevention, AML/CFT/PSE rules and regulatory licensing requirements (if applicable) at Bitvavoās sole discretion; and
(d) Bitvavo has accepted this person as a Participant.
4.2 Participant categories
Bitvavo distinguishes four categories of Participants:
(a) Retail Participants;
(b) Corporate Participants;
(c) Market Makers; and
(d) Brokers (including, but not limited to, providers of trading bots or other services through the Bitvavo API).
4.3 Retail Participants
A Retail Participant can be a natural person that is at least 18 years old, that is not a US Person and that is resident in a jurisdiction in the EEA where BitvavoāServices are available.Ā
4.4 Corporate Participants
A Corporate Participant can be a legal entity that is not a Market Maker or a Broker and that is resident or established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its Services.
4.5 Market Makers
A Market Maker can be a natural person or legal entity that has entered into a market making agreement with Bitvavo and that complies with the terms thereof, the User Agreement and any other agreement concluded with Bitvavo or Bitvavo Custody. A market making agreement includes specific terms and conditions to obtain access to the Bitvavo Trading Platform as a Marker Maker, such as, amongst others, the Digital Assets covered by the market making agreement, minimum up-times and response times, the streaming of prices/quotes on both sides of the market, spread limits, fees, credit lines, incentives and penalties for non-compliance.Ā
4.6 Brokers
A Broker can be a legal entity that is a resident or is established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its Services, and, if applicable, is authorised to provide Crypto-Asset Services as defined in MiCA, and that complies with the terms of any agreement with Bitvavo.
4.7 API Trading Bots
A provider operating one or more Trading Bots that wants to access the Bitvavo Trading Platform must agree to the Bitvavo Developer Agreement and/or the API Partner Agreement.
4.8 Trading limits
(a) Bitvavo applies trading limits to the Account of Participants, including daily, weekly, monthly, annually and total limits. Bitvavo may set such limits in its sole discretion, based on the information provided by Participant and any other information available to Bitvavo (including, but not limited to, the Account balance of the Participant, the trading behaviour of the Participant, the capacity and resilience of the Bitvavo Trading Platform and the market for each relevant Digital Asset).
(b) Bitvavo may include the different trading limit thresholds as an indication on its Website. Bitvavo can amend the procedures and limits from time to time without prior notice and with immediate effect.
(c) Bitvavo may require a Participant to provide or verify additional information, or to wait some period of time after execution of a trade or a transaction, before settlement of such trade and before permitting a Participant to enter into any subsequent trades on the Bitvavo Trading Platform.
(d) A Participant may submit a request for higher limits. Bitvavo may require the Participant to submit additional documentation in this regard and does not guarantee that limits will be raised as requested.
5.1 Trading Days and Trading Hours
The Bitvavo Trading Platform is available for trading every day, 24 hours per day, except for scheduled or unscheduled down-time. Specific trading conditions may apply from time to time, for all admitted Digital Assets or on an asset-by-asset basis, for example during a specific status as determined by Bitvavo, including Halted markets, Cancel Only markets or during Auction periods, as set out in these Trading Rules.
5.2 Transactions
(a) Participants can submit instructions to buy or sell Digital Assets on the Bitvavo Trading Platform (placing an Order), against other Digital Assets or Bitvavo E-Tokens, where pairs are offered by Bitvavo from time to time (geographical restrictions may apply).
(b) Bitvavo is not a Participant and Bitvavo will not act as a counterparty of a Participant in any transaction in Digital Assets executed on the Bitvavo Trading Platform.
(c) The Participant is solely responsible for placing Orders and providing any other instructions.Ā
(d) Bitvavo or other Participants may provide information on Digital Assets, including, but not limited to, the price and volatility. This information as well as any other information on the Bitvavo Trading Platform does not constitute investment advice, a recommendation to sell or buy or an opinion of Bitvavo.
(e) The price indicated on the transaction confirmation is the price at which an Order has been executed. This price may deviate from prices indicated or referenced on the Bitvavo Trading Platform prior to the execution of an Order. The price indicated on the transaction confirmation is always conclusive over other price indications.
5.3 Recurring Buy
(a) Participants can automatically buy selected Digital Assets on a monthly basis by switching on the āRecurring Buyā feature.
(b) By using this feature, Participants authorise Bitvavo to deduct Funds and Fees directly from their Account at a random timestamp on a certain day of each month as selected by the Participant.
5.4 Holding of Funds
Once an Order to buy Digital Assets is placed, a certain amount of Funds is placed on hold in the Participantās Account. This means that these Funds can only be used to fulfil the Order for which they are reserved. The amount of Funds that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Funds on hold accordingly.Ā
5.5 Holding of Digital Assets
Once an Order to sell Digital Assets is placed, a certain amount of Digital Assets is placed on hold in the Participantās Account. This means that these Digital Assets can only be used to fulfil the Order for which they are reserved. The amount of Digital Assets that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Digital Assets on hold accordingly.
5.6 Order Routing
(a) If a Participant has enabled Price Guarantee Service, Orders that are eligible for Price Guarantee Service that are submitted by the Participant are considered an RfQ (request for quote) and will be routed to the RfQ Segment.Ā
(b) All other Orders will be routed to the CLOB segment.
5.7 Market Specifications
(a) Bitvavo will publish Market Specifications detailing the terms of any Digital Assets admitted to trading on the Bitvavo Trading Platform.
(b) Bitvavo may amend, at its sole discretion, the Market Specifications and such amendments shall be communicated to Participants on reasonable notice.Ā
5.8 Cancellation of transactionsĀ
Bitvavo may, in its sole discretion, or following a request by a Participant, conduct a review of a transaction executed on the Bitvavo Trading Platform where there is a reasonable basis to believe that such transaction has been executed as a result of an erroneously submitted Order, or executed in violation of applicable laws and regulations (including market abuse) and these Terms or where so requested by competent authorities or courts.
5.8.2. Bitvavo shall notify the relevant Participants to a transaction of the result of an investigation into one or more transactions.Ā
5.8.3. If Bitvavo, at its sole discretion, determines the transaction subject to an investigation is clearly erroneous or executed in violation of applicable laws and regulations (including market abuse) and these Terms, or where so requested by competent authorities or courts. it may nullify the transaction, un-wind the fund movements resulting from the transaction and shall notify the affected Participant(s) accordingly.Ā
6.1 Order Options
(a) The main Order options available on the Bitvavo Trading Platform are a Market Order or a Limit Order.
(i) Market Order:
(A) A Market Order is matched with the best-priced Limit Order in the Order Book at the time of the request. If there are more than one such Limit Orders, the Market Order is matched with the oldest one.Ā
(B) There is no guarantee that a Market Order will fill at the market price indicated. A Market Order may fill at a number of different prices, based on the quantity of the Market Order and the quantities and direction of the existing Orders in the Order Book at the time.
(ii) Limit Order:
(A) A Limit Order is an Order to buy or sell at a fixed price.Ā
(B) A Limit Order will be executed if or when the market price reaches the limit price and will be filled at the limit price or better.
(1) A buy Limit Order will be executed only at the limit price or a lower price.
(2) A sell Limit Order will be executed only at the limit price or a higher price.
(b) Additional advanced order options that may be available on the Bitvavo Trading Platform are Stop Loss Order, Stop Loss Limit Order, Take Profit Order and Take Profit Limit Order. The availability of these order options may depend on the method of access to the Bitvavo Trading Platform.
(i) Stop Loss Order:
(A) A Stop Loss Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches a specified trigger price in order to limit Participant losses.Ā
(B) Once a Stop Loss Order has been placed, it is considered āactiveā until cancelled or until the relevant Market Order is placed, when the Stop Price has been triggered.Ā
(C) A Stop Loss Order is not posted to the Order Book and is not visible to other Participants.
(ii) Stop Loss Limit Order:
(A) Stop Loss Limit Order mechanics are similar to Stop Loss Order with the main difference that Stop Loss Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
(iii) Take Profit Order:
(A) A Take Profit Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches the Take Profit Price to realise Participant profits.Ā
(B) Once a Take Profit Order has been placed, it is considered āactiveā until it is cancelled or until the relevant Market Order has been placed when the Trigger Price is reached.Ā
(C) A Take Profit Order is not posted to the Order Book and is not visible to other Participants.
(iv) Take Profit Limit Order:
(A) Take Profit Limit Order mechanics are similar to Take Profit Order with the main difference that Take Profit Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
6.2 Submission and execution of OrdersĀ
(a) An Order is submitted by a Participant via the App, Website or API. The Participant selects the Digital Asset it wants to buy or sell and enters the Order details. Subsequently, the Participant submits the Order to the Order Book.Ā
(b) Once the Order is submitted by the Participant and received by the Bitvavo Trading Platform system, Bitvavo performs a validation of the Order details, including if the Participantās balance is sufficient, the market protection checks as set out in Section 6.3 of these Trading Rules and whether, in Bitvavoās sole discretion, the Order contains all the relevant datapoints as pertaining to the Order, including datapoints that are required for Bitvavo to comply with applicable regulations or any other datapoints to be included in any Order. If the Order fails any of these checks, the Order is rejected and the Participant is notified. If the Order passes these checks, the Order is accepted by Bitvavo, entered into the Order Book and the Participant is notified.
(c) Once accepted into the Order Book, the Order is either matched with another existing Order in the Order Book with an opposite direction, or is added to the Order Book. If an Order is matched with another Order, this results in the execution of the Order in line with Section 6.5 - 6.8 of these Trading Rules. The Participant receives confirmation of such execution.
(d) An Order has the following parameters:
(i) Market: Name of the market, in the format BASE-QUOTE (e.g. BTC-EUR).
(ii) Side: Buy or sell.
(iii) Order Type: Limit Order or Market Order. When placing a Limit Order, the Order might still be executed against a better price than specified, in which case it is processed as a Market Order. There is also a possibility to submit advanced order types as described in [Section 6.3].
(iv) Amount: The quantity of the base asset to be bought/sold (required for Limit Orders, optional for Market Orders). Applicable quantity decimal precisions are detailed in the relevant Market Specification.
(v) Amount Quote: The amount specified in the quote asset (optional for Market Orders, either Amount or Amount Quote is required)
(vi) Price: The price for base asset specified in the quote asset (Required for Limit Orders). Applicable tick sizes are detailed in the relevant Market Specification.
(vii) Time In Force: This specifies how long the Order should be placed on the Order Book. This only applies to Limit Orders. The following options are allowed:
(A) GTC: Good-Til-Cancelled. This is the default setting and places an order on the Order Book until it is filled or cancelled.
(B) IOC: Immediate-Or-Cancel. This allows (partial) filling of the Order when it is submitted. The remaining amount that cannot be matched immediately will be cancelled.
(C) FOK: Fill-Or-Kill. This ensures that the entire Order is either filled or cancelled. Partial fills are not possible.
(viii) Self-Trade Prevention: Trading with oneself is not allowed. This setting handles what should be done if a Participantās Order would match with one of the Participantās own orders. The following options are allowed:
(A) Decrement And Cancel: This is the default setting and modifies both Orders by the amount that would have been filled. This results in the smaller of the two Orders being cancelled, and the other Order being reduced in size.
(B) Cancel Oldest: Cancels the oldest Order.
(C) Cancel Newest: Cancels the newest order.
(D) Cancel Both: Cancels both Orders.
(ix) Post Only: Limit Orders that have this set to true will be cancelled if matched immediately. This ensures that the Participant pays the maker fee and not the taker fee. As a default, Post Only is switched off.Ā
(x) Response Required: If this value is set to false, only the Order ID of the newly created Order is returned. The default value is true (i.e. a full response).
6.3 Market Protections
(a) Order Minimums/Maximums
All Market Orders, Limit Orders, and Stop Orders placed on the Bitvavo Trading Platform are subject to minimum and maximum Order Amount and Amount Quote requirements per market.
(b) Number of Open Orders
All Participants are subject to a maximum number of Orders that may be open in the Order Book per market. When a Participant reaches the limit in a given market, any Orders entered in that market thereafter are rejected until the number of open Orders stored in the Order Book for the given market decreases below the limit.
(c) Placement Price Protection
Limit Orders with a Good-Till-Cancel Time in Force are subject to a Placement Price Protection. Buy (Sell) Limit Orders with a price lower (higher) than the lower (upper) Placement Price Protection Band will be rejected.Ā
(i) The Upper Placement Price Protection Band is calculated by multiplying the Placement Price Multiplier times the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed.
(ii) The Lower Placement Price Protection Band is calculated by dividing the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed by the Placement Price Multiplier.
(d) Execution Price Protection
Limit Orders are subject to an Execution Price Protection. Buy (Sell) Limit Orders with a price higher (lower) than the upper (lower) Execution Price Protection Band will be rejected.
(i) The Upper Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed plus the Execution Protection Threshold percentage.
(ii) The Lower Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed minus the Execution Protection Threshold percentage.
(e) Spread Price Protection
(i) Market Orders are subject to a Spread Price Protection. Market Orders will fill at prices up to the Spread Protection Threshold from the mid-point price between the best bid and best offer on the Order Book at the time the Market Order is placed. If a Market Order would fill against Orders beyond the Spread Protection Threshold, the Order will partially fill up to the Spread Protection Threshold level and all the remaining quantity of the Order will be cancelled.
(f) Reference Price Protection
All Orders are subject to Reference Price Protection, which limits how far the price at which an Order is executed, can deviate from the market price at the time the Order is placed (the āReference Priceā).
The Reference Price is an index price, calculated using price data from multiple external exchanges to reflect a fair market value for the Digital Asset. Orders will only be filled at prices within what is known as the āReference Price Protection Thresholdā, which is a defined range from this Reference Price. If the price at which an Order would be filled falls outside this threshold, only the portion of the Order within the threshold will be filled; the rest will be cancelled. This may result in some Orders being partially filled.
If a valid reference price is unavailable, or if Bitvavo determines that the index does not accurately represent current market conditions, this protection will not apply.
(g) General Note for this section
The limits, multipliers and thresholds used for this section 6.3 shall be determined by Bitvavo for each market.
6.4 Errors
(a) In exceptional cases, there may be errors in the Bitvavo Trading Platform, including in relation to the prices displayed or the way in which Orders are matched. In addition, the Digital Assets on the Bitvavo Trading Platform may be subject to unusual price movements, including as a result of market manipulation or sudden drops or spikes in liquidity. In such cases, Bitvavo may at its sole discretion (and is in no way obliged to):
(i) retrospectively correct any such errors or rectify any such price movements, including by amending or reverting transactions, which may be to the advantage or to the disadvantage of Participant; or
(ii) temporarily or indefinitely halt trading on the Bitvavo Trading Platform for one or more Digital Assets;
(b) Especially during periods of high volume, illiquidity, fast movement or volatility, any Digital Assets traded on the Bitvavo Trading Platform may be executed at a different rate than displayed to the Participant at the time of Participants Order.
(c) In the case of suspected fraud or misuse, Bitvavo reserves the right to suspend or cancel Orders and transactions until the legitimacy has been verified.
6.5 Order Matching and Execution during Regular Trading
(a) Orders that are matched immediately are taker orders. Orders that are not matched immediately and are placed in the Order Book are maker orders.Ā
(b) Limit Orders may be maker or taker orders, depending on whether the Limit Order can be matched immediately. If matched immediately, the Limit order is a taker order. If placed on the Order Book, the Limit Order is a maker order.
(c) Orders are matched based on price-time priority. This means that taker orders are matched with the maker orders with the best available price. If several orders have the same price, the oldest maker order is matched. This process continues until the order is filled, placed on the Order Book, or cancelled.
(d) The price paid/received is determined by the maker order. This means that Limit Orders can be filled at prices better than their limit price.
(e) Fills may be settled nearly instantly or after a period of time.
(f) The execution price of a Market Order may differ significantly from the indicated price. This may be due to a change in price between the time of the Order being initiated by the Participant and the execution of the Order (i.e. 'slippage').
(g) Market Orders, Limit Orders, and Stop Limit Orders are not guaranteed executable due to the required availability of sufficient supply or demand.
(h) Orders may be executed instantly or after a period of time and will be considered to have taken place at the execution date and time.
6.6 Order Matching during Halted Markets
(a) Bitvavo may, in its discretion, temporarily halt trading in a market to preserve market integrity, orderly trading conditions, and/or to conduct regular scheduled maintenance.
(b) Orders cannot be placed, modified or cancelled when a market is Halted.
(c) No order matching occurs when a market is Halted.
(d) No Order Book updates will be broadcasted when a market is Halted.
6.7 Order Matching during Cancel Only Markets
(a) Bitvavo may, in its sole discretion, temporarily set Cancel Only in a market to preserve market integrity and/or to conduct regular scheduled maintenance.
(b) Orders can be cancelled when a market is in Cancel Only status.
(c) Orders cannot be placed or modified when a market is in Cancel Only status.
(d) No order matching occurs when a market is in Cancel Only status.
6.8 Order Matching during Auctions
(a) Bitvavo employs an Auction methodology after a market has been Halted or put into Cancel Only before Regular Trading resumes to guarantee price discovery and orderly markets.
(b) The Auction process consists of two phases:
(i) Auction Collection:
(A) A Participant cannot place a Market Order when a market is at the Auction Collection phase.
(B) A Participant can place, modify or cancel all other Order types when a market is at an Auction Collection phase.Ā
(C) No Orders will be matched during the Auction Collection.
(ii) Auction Matching:
(A) A Participant cannot place, modify or cancel Orders when a market is at the Auction Matching phase.
(B) During this period, Orders will be matched in accordance with the procedure as set out below.
(C) Active Limit Orders are used to determine the price at which the most units of the base asset are traded. If there is no price where trades occur, no matching occurs and Regular Trading resumes.
(D) If a price is obtained in the previous step, this price is used to prevent self-trades (according to the specifications made by the User regarding the treatment of its Orders for self trade prevention) .
(E) Orders are matched based on price-time priority and all Orders are considered taker orders. Limit Orders with the best price will be filled first, at the price determined in step (1).
(F) When no more Limit Orders can be matched at the determined price, Buy Post-Only Orders with a price above the determined price and Sell Post-Only Orders with a price below the determined price are cancelled and Regular Trading resumes.
(c) No Order Book updates will be broadcasted when a market is at Auction phase.
7.1 Price Guarantee ServiceĀ
The Price Guarantee Service protects the Participant against price fluctuations in a specific Digital Asset for a period of 5 seconds upon submission of the Order. This market risk is absorbed by the Participant interacting on the RfQ Segment and responding to RfQ. To account for the market risk taken by the Participant between the time of the Participantās quote and the execution of the Order, each quote may include a compensation (spread).Ā
7.2 Price Guarantee TradesĀ
(a) An Order via the Price Guarantee Service will result in a trade when the Participant has accepted the quote that has been shown to it in response to the opening of the order form and the entering of the relevant details of the order by the Participant.Ā
(b) If a quote under the RFQ Segment is accepted in a timely manner by a Participant, the RfQ will be executed under the Price Guarantee Service terms set out herein, and such RfQ will be deemed a taker order of that Participant.
7.3 Price Guarantee Quoting Process
If a quote is not accepted by a Participant within five (5) seconds, the quote will be refreshed with a new quote, which will again be valid for five (5) seconds. This process is repeated until a Participant accepts a quote, which will result in a (partial or entire) execution of the PG Order. Alternatively, the process ends when a Participant does not accept a quote and exits the order form for a specific crypto pair.
7.4 Quotes on the RFQ Segment
Prices of the quotes provided by Participants interacting on the RfQ Segment in response to RfQ must remain within a predetermined range. Only quotes that fall within this range will be considered by Bitvavoās matching engine in selecting the best quote (best from the Participant's perspective) that will be displayed to the Participant in response to a given RfQ.Ā
7.5 Algorithmic Trading
Participants may engage in Algorithmic Trading on the Bitvavo Trading Platform provided that:Ā
(a) the Participant has given prior notice to Bitvavo each time it wishes to deploy a new algorithm or a material change to an algorithm on the Bitvavo Trading Platform and provide a description of the algorithm including a unique identification number assigned to such algorithm, which shall be included in any order or quote generated or governed by such algorithm. Participant shall update such details and identification number upon each material change of the algorithm;
(b) prior to deployment of any algorithm on the Bitvavo Trading Platform, the Participant has performed appropriate and successful testing of each algorithm ensuring an algorithm does not contribute to or create disorderly market conditions on the Bitvavo Trading Platform;
(c) upon Bitvavoās instruction, the Participant shall use the testing environment made available by Bitvavo for purposes of conformance testing any new algorithm or substantial change to an algorithm, prior to deployment on the Bitvavo Trading Platform;
(d) each algorithm on the Bitvavo Trading Platform shall comply with Bitvavoās Trading Rules and applicable regulations;
(e) upon Bitvavoās request, the Participant shall provide certification in writing of the successful testing for each algorithm to be deployed on the Bitvavo Trading Platform, including for each substantial change thereto prior to the deployment on the Bitvavo Trading Platform;
(f) each of their algorithms deployed on the Bitvavo Trading Platform is continuously monitored by the Participant to prevent disorderly trading.
(g) the participant complies with all applicable regulatory obligations, including those relating to the prevention of market abuse, money laundering, terrorism financing, sanctions, and any relevant licensing or authorisation requirements.Ā
7.6 Conditions to High Frequency Trading
Bitvavo may, in its sole discretion, apply conditions to the deployment of High Frequency Trading techniques on the Bitvavo Trading Platform.
8.1 Grounds for Suspension
Bitvavo may, in its sole discretion, suspend or remove one or more Digital Assets or Participants from trading or to suspend trading on the Bitvavo Platform in its entirety or for an individual Participant. Among others, Bitvavo can do so in the following circumstances:
(a) to prevent disorderly market conditions;
(b) upon the substantiated request of an Issuer;
(c) in case of (suspected) fraud, deception or market abuse;
(d) failure of an Issuer or a Participant to comply with these Trading Rules;
(e) failure of an Issuer or a Participant to comply with applicable legislation;
(f) in case of bankruptcy of an Issuer or a Participant;
(g) failure of an Issuer or a Participant to provide requested information to Bitvavo, or a supervisory authority;
(h) in case of technical or operational disruption;
(i) in case of the occurrence of events in the financial markets or the Digital Asset markets that may have material adverse effect on the orderly trading, integrity or resilience of the Bitvavo Trading Platform; or
(j) if deemed appropriate by Bitvavo in its sole discretion in order to protect the integrity or resilience of the Bitvavo Trading Platform, or to protect the interests of any Participant, Bitvavo or any affiliate of Bitvavo.
8.2 Request from Supervisory Authority
Bitvavo will comply with a request of a supervisory authority to suspend or prohibit trading as referred to in Section 17 of these Trading Rules.
8.3 Suspension of Trading for Maintenance
Bitvavo may temporarily suspend trading for maintenance or for other reasons. Generally, Bitvavo will proceed according to the following steps:
(a) Announcement scheduled downtime: Participants will be informed through a message on account.bitvavo.com.
(b) Scheduled downtime begins: Participants will be informed through a message on account.bitvavo.com.
(c) Scheduled downtime ends: Markets will be placed in Halted mode. Participants will be informed through a message on account.bitvavo.com when trading resumes. This will be at least 15 minutes after the scheduled downtime ended.
8.4 Market Status during and after Suspension
During a suspension, the Bitvavo Trading Platform will be placed in Halted mode. When trading resumes after a suspension, Bitvavo will apply the Auction methodology as referred to in Section 6.8 of these Trading Rules.Ā
9.1 Settlement of Digital Assets
Bitvavo is responsible for the correct execution and settlement of the purchase and sale of Digital Assets on the Bitvavo Trading Platform in accordance with applicable regulations.
9.2 Off-Chain Settlement
All transactions on the Bitvavo Trading Platform are settled off-chain. Final settlement is generally initiated immediately or shortly after execution of a transaction on the Bitvavo Trading Platform and by the end of the Trading Day at the latest. The settlement process results in the transfer of rights associated with the traded Digital Assets from one Participant to another against the payment of the transaction price, while the Digital Assets themselves continue to be held by the Foundation, but on behalf of the acquiring Participant.
10.1 Pre-Trade Transparency
Bitvavo publishes the bid and ask prices and the depth of trading interest at those prices which are advertised on the Bitvavo Trading Platform for Digital Assets in accordance with applicable regulations. Bitvavo makes this information available on a continuous basis on its website.
10.2 Post-Trade Transparency
Bitvavo publishes the price, volume and time of the transactions executed in respect of Digital Assets traded on the Bitvavo Trading Platform in accordance with applicable regulations. Bitvavo publishes this information as close to real-time as technically possible in the App and on the Website.
10.3 Access to this Information
Bitvavo makes available the information in this section on a non-discriminatory basis. The regulatory information will be made available free of charge 15 minutes after publication in a machine-readable format, and it will remain published for at least two years.
11.1 Modification and Termination of Trading
Bitvavo may, in its sole discretion, for any reason and without liability to Participant, (i) modify, discontinue or terminate, temporarily or permanently, part or all of its Trading Services in general, and (ii) suspend, restrict or terminate Participantās access to the Bitvavo Trading Platform.
11.2 Bitvavo Trading Platform Availability
All Services are provided on an āas isā and āas availableā basis without warranty of any kind. Bitvavo does not guarantee that the Bitvavo Trading Platform will be available for any absolute or relative amount of time. Bitvavo does not warrant that access will not be interrupted or that there will be no delays, failures, errors, loss or similar of transmitted information. This may include, but is not limited to, unavailability of any of the Services during times of high volume, illiquidity, fast movement or volatility.
11.3 No Obligation to Provide Services
Bitvavo has no obligation to make available the Bitvavo Trading Platform to anyone when Bitvavo may reasonably believe that this would violate applicable laws and regulations.
12.1 Access to Bitvavo Trading Platform via API
Bitvavo may provide access to Participants to the Bitvavo Trading Platform and specific data and information through an āApplication Programming Interfaceā (API) which may be subject to additional terms and conditions as set by Bitvavo from time to time.
12.2 Use of API
To use the API, one or more API key(s) with corresponding secrets (API Credentials) must be created. The Participant is solely responsible for safeguarding the API Credentials and for any activities by the Participant or third parties that have access to the Account, whether authorized or not. In the event that the Participant knows, or should know, that API Credentials have been stolen or misused, the Participant shall contact Bitvavo immediately.
12.3 Changes to API
Bitvavo may, in its sole discretion, add, discontinue or remove, in whole or in part, the API at any time and without notice. Bitvavo cannot guarantee that future versions of the API will be backwards compatible. Participant acknowledges and understands that any of these changes may adversely affect Participantās use of the API and might require the Participant to make substantial changes in order to continue using the API, and that this is the Participantās own responsibility.
12.4 API Scope and Modifications
The scope and concrete form of the API is at Bitvavoās sole discretion. The API may be modified or abandoned at Bitvavoās sole discretion.
12.5 Monitoring of API use
Bitvavo may monitor the use of the API. The Participant will not block or otherwise interfere with the monitoring process.
12.6 API Limits
Bitvavo may set limits on the number of messages or Orders that the Participant can transmit through the API or extend limits for other Participants, in its sole discretion, during any given period and without notice. The Participant shall not attempt to circumvent such limitations. If the Participant exceeds the limits, Bitvavo may moderate the Participant activities, may cease offering access to the API or may immediately suspend or terminate access to the API in its sole discretion and without notice.
12.7 Prohibited Use of the API
The Participant shall not, and shall not encourage or authorize others to:
(a) use the API in any manner that is not expressly authorized by the User Agreement and the Trading Rules;
(b) alter, reproduce, adapt, distribute, display, publish, reverse engineer, translate, disassemble, decompile or otherwise attempt to create any source code that is derived from the API;
(c) use or access the API for purposes of monitoring the availability, performance, or functionality of any of the Services or for any other benchmarking or competitive purposes;
(d) collect, cache, aggregate, or store data or content accessed via the API other than for purposes allowed under the User Agreement;
(e) use the API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise impacts the stability of Bitvavoās servers or impacts the behaviour of other applications using the API;
(f) attempt to cloak or conceal Participantās identity when requesting authorization to the API;
(g) use the API to (i) access or use any information not permitted by the User Agreement and these Trading Rules, to (ii) circumvent or break any of Bitvavoās administrative, technical or organizational security measures, (iii) disrupt, impair, overburden or degrade the API or the Services, (iv) change the API or the Services in any way, or (v) test the vulnerabilities of the Services or API; and
(h) use any data collected from Participantās use of API for advertising purposes.
13.1 Access to Market Data
All Participants have full and equal real-time access to market data. Market data is made available through the web interfaces and Bitvavo API.
13.2 Equal Opportunity
All Participants have equal opportunity with regard to access the web interfaces and Bitvavo API.
14.1 Market Abuse
Participants are prohibited from engaging in market abuse, including insider dealing and market manipulation as referred to in Title VI MiCA.Ā
14.2 Market Abuse - Prohibited Activities
Without prejudice to the prohibitions as set out in Title VI MiCA, Participants are prohibited from any behaviour that may constitute market abuse, including but not limited to carrying out the following activities on the Bitvavo Trading Platform:
(a) Pump and dumps: artificially inflating the price of a Digital Asset through false and misleading positive statements, in order to sell the cheaply purchased Digital Asset at a higher price.
(b) Wash trading: Simultaneously buying and selling the same Digital Assets to create false trading volume and artificially inflate market activity.
(c) Front-running: Trading in advance of a large client order to take advantage of anticipated price movements resulting from the execution of that order. Front running involves using non-public information about future or pending transactions for their own benefit.
(d) Churning: excessive trading activity by (Broker) Participants on behalf of their clients, on either side of the Order Book, intended to increase the Participantās (Broker) commissions.
(e) Quote stuffing: quickly entering and then withdrawing large orders in an attempt to flood the market with quotes, causing competitors to lose time in processing them or causing other disorderly trading conditions.
(f) Spoofing / layering: creating the illusion of pessimism (or optimism) in the market by placing buy or sell orders without the intention of filling them.
(g) Insider trading: trading in Digital Assets based on non-public information that could affect the price of those Digital Assets.
(h) Information-based market abuse: spreading false or misleading information about crypto companies, crypto projects, Digital Assets, or market conditions to influence prices or trading activity. This includes disseminating rumours, false news, or deceptive market commentary to manipulate market participants perceptions.
(i) Improper disclosure practices: failing to disclose non-public information that could affect market prices or engaging in selective disclosure of information to certain market participants. Misleading disclosures or inadequate transparency about financial performance, risks, or other material matters related to a Digital Asset can also constitute market abuse.
14.3 Prohibition to use the Account and the Services for criminal activity
A Participant may not use the Account and the Services to perform criminal activities of any sort, including but not limited to money laundering, terrorist financing, sanction evasion, fraud or any other criminal or illegal activity, the existence whereof is to be determined by Bitvavo at its sole discretion. These include, but are not limited to, the following:
(a) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to sanctions programs administered in the countries where Bitvavo conducts business, including but not limited to the EU Sanctions list.
(b) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to terrorist financing as applicable in the countries where Bitvavo conducts business.
(c) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to money laundering as applicable in the countries where Bitvavo conducts business.
(d) Activity which would be related to fraud such as activities which operate to defraud Bitvavo (including Participants providing any false, inaccurate, or misleading information to Bitvavo), Participants and/or other persons.
(e) Activity which would be related to drugs such as sale of narcotics, controlled substances, and any equipment designed for making or using drugs.
(f) Activity which would be related to multi-level marketing such as pyramid schemes and network marketing.
(g) Activity which would be related to unfair, predatory or deceptive practices such as investment opportunities or other services that promise (too) high rewards and sites that Bitvavo determines in its sole discretion to be unfair, deceptive, or predatory towards Participants.
(h) Activity which would be related to illegal gambling such as unregulated lotteries, sports forecasting or odds making and comparable activities.
(i) Activity which would be related to high-risk businesses such as any businesses that Bitvavo believes to pose elevated financial risk, legal liability, or violates bank policies.
(j) Activity which would be related to (attempts to) to reverse engineer, modify, translate or disassemble the (software behind the) Bitvavo Environment in whole or in part.
14.4 Reporting to the AFM
Bitvavo will report to the AFM if it has any reasonable suspicion regarding an order or transaction, including any cancellation or modification thereof, and other aspects of the functioning of the distributed ledger technology such as the consensus mechanism, where there might exist circumstances indicating that market abuse has been committed, is being committed or is likely to be committed.
14.5 Reporting to Bitvavo
Each Participant must promptly report any suspicious activity to Bitvavo that undermines the integrity and fairness of crypto markets, that could be identified as market abuse as referred to in Title VI MiCA and/or that can be identified as one of the activities listed in this section.
14.6 Notification to Authorities
Bitvavo is authorized to notify the relevant authorities and will provide data to the relevant authorities to the extent required by law and regulation.
14.7 Reporting of Unusual Transactions
Bitvavo will report any unusual transactions to the relevant authority in line with the applicable anti-money laundering and anti-terrorism financing legislation.
15.1 Cancellation of Orders
Bitvavo may modify or cancel open Orders for any reason, including but not limited to, the following circumstances, the occurrence of which is to be determined by Bitvavo in its sole discretion:
(i) in case of Orders placed by Participants who, in Bitvavo's sole discretion, may have engaged or may have attempted to engage in abusive use of the Bitvavo Trading Platform in relation to that Order or otherwise. This may include market abuse activities or other prohibited activities as referred to in Section 14 of these Trading Rules, but may also include operational or otherwise abusive or adverse activities, such as using the API in a manner which unreasonably burdens the Bitvavo Trading Platform;
(ii) in case of Orders which involve an error with respect to price, quantity, or other parameters;
(iii) if required by any applicable law or regulation;Ā
(iv) upon instruction of competent authorities or court order; or
(v) if required for technical reasons.
15.2 Suspension of Account
Bitvavo may suspend or block specific or all use of an Account, suspend or cancel any pending Order or PG request (including any requests to modify or cancel an Order), any transaction, suspend or cancel any deposit or withdrawal, freeze the Funds or Digital Assets related to an Account or suspend the cancellation of an Account in connection with an investigation into misuse of an Account or any Service provided by Bitvavo. If the legitimacy of any Participant or any Order, PG request or use of the Services cannot be established, such Participant may lose all rights to the Funds and Digital Assets in its Account.
15.3 Delisting
Bitvavo may at any time and in its sole discretion decide to delist Digital Assets from the Bitvavo Trading Platform. Bitvavo can do so in any circumstances, including, but not limited to:
(a) a breach of these Trading Rules by the Issuer or non-conformity of the relevant Digital Asset with these Trading Rules;
(b) any events or developments regarding the Issuer or the Digital Asset that could pose material risk to the Participants or orderly trading on the Bitvavo Trading Platform;
(c) upon the request of a supervisory authority;
(d) in case of bankruptcy of the Issuer;
(e) if the Digital Asset is outside of the risk appetite of Bitvavo;
(f) upon the substantiated request of the Issuer of the Digital Asset;
(g) in case of material changes to the Issuer or the Digital Asset; or
(h) The Digital Asset fails to meet pre-set minimum liquidity thresholds; or
(i) the Digital Asset does not comply with Section 3.5 of these Trading Rules.
15.4 Consequences of Delisting
Upon delisting of a Digital Asset, trading in the Digital Assets concerned will be discontinued. Bitvavo will, where possible, timely inform of any (planned) delisting arrangements and be given the opportunity to divest or trade-away Digital Assets that are subject to delisting.
16.1 Instructions from supervisory authorities
Bitvavo shall comply with instructions from supervisory authorities, including EBA and the AFM, which may result in suspension or delisting of (Digital Assets.
16.2 Access to Information
Bitvavo shall comply with requests from supervisory authorities to provide relevant data relating to Orders in Digital Assets that are advertised through its systems, or to provide access to the Order Book, or to records of transactions executed on the Bitvavo Trading Platform. Relevant data may include details of any Order or transaction, as the case may be, including personal data and other datapoints that link Orders with transactions executed on the Bitvavo Trading Platform.Ā
17.1 Fees for admitting to trading on Bitvavo Trading Platform
Bitvavo may charge fees for the admission to trading on the Bitvavo Trading Platform as well as periodic fees in order to remain listed and available for trading on the Bitvavo Trading Platform.
17.2 Fees for trading on the Bitvavo Trading Platform
(a) Participant shall be due fees to Bitvavo for trading on the Bitvavo Trading Platform.
(b) Any fees and the relevant fee amounts shall be published by Bitvavo on the designated fee information pages on the Website and/or the Bitvavo Environment (the Fee Schedule), as amended from time to time, or shall be made available to Participant otherwise. Bitvavo may make changes hereto in its sole discretion from time to time. Any changes made available to participants shall become effective directly.
17.3 Trading Fee Structure
(a) Trading fees on the Bitvavo Trading Platform are based on each Participant's trading volume from the previous 30 days in accordance with the Fee Schedule as published on the Bitvavo website from time to time.
(b) The total fee amount that is charged for a trade depends on the following:
(i) the total cost (value) of the Order;Ā
(ii) the Currency Pair that is being traded;Ā
(iii) the 30-day trading volume of the participant; and
(iv) whether an Order is Maker or Taker.
17.4 Calculation of the Fees
(a) The fee is charged (and rebates are given) in the quote asset.
(b) Fees are calculated for each fill.
(c) Fees are rounded up, to the precision of the asset.
(d) Fees are averaged for each Order. This means that if one fill has paid more in fees than required, the next fill pays a lower fee, so that the average fee paid equals or exceeds the fee tier the Participant is in. This process may be conducted manually after the settlement has been done.Ā
(e) The 30-day rolling volume used to determine the fee tier is calculated in EUR, at 00:00 UTC each day.
(f) All Participants pay the fees mentioned in the Fees Schedule.Ā
(g) Bitvavo may temporarily increase or decrease the fee tier for Market Makers and large institutions (determined on a case-by-case basis).
17.5 Payment of Fees
Bitvavo may charge any fees and costs to the Participant, including but not limited to trading fees, by deducting these from Participantās Funds, Digital Assets or Bitvavo E-Token Wallet.
Bitvavo reserves the right to amend, add, or remove parts of the Trading Rules at any time and in its sole discretion. Participant will be notified of any changes and although Bitvavo will endeavour to provide Participant with advance notice, Bitvavo may indicate that the revised Trading Rules shall be effective immediately. If Participant does not agree with any such modification, Participant must close its Bitvavo Account and cease using the Bitvavo Trading Platform. If Participant continues to use the Bitvavo Trading Platform after a modification, Participant is deemed to have accepted and agreed to the amendments. It is the Participant's responsibility to review the amended Trading Rules.
1.1 Account has the meaning given thereto in the User Agreement.
1.2 AFM means the Dutch Authority for Financial Markets (Autoriteit Financiƫle Markten).
1.3 Algorithmic Trading means the use of computer algorithms that automatically determine individual parameters of orders resulting in investment and/or execution decisions based on predefined criteria and strategies with limited or no human intervention.
1.4 Affiliate has the meaning given thereto in the User Agreement.
1.5 API means Application Programming Interface.
1.6 API Credentials means the API key(s) with corresponding secrets.
1.7 API Trading Bot means an automated software application that interacts with the Bitvavo Trading Platform via API to execute trades based on predefined algorithms or strategies.
1.8 App has the meaning given thereto in the User Agreement.
1.9 Auction means the process as described in Section 6.8 of these Trading Rules.
1.10 Broker means a Participant as referred to in Section 4.6 of these Trading Rules.
1.11 Bitvavo means Bitvavo B.V.
1.12 Bitvavo Custody means Bitvavo Custody B.V.
1.13 Bitvavo E-Token has the meaning given thereto in the User Agreement.
1.14 Bitvavo Trading Platform means the Digital Asset trading platform operated by Bitvavo.
1.15 Cancel Only means the status of the Bitvavo Trading Platform whereby Participants are restricted to cancelling existing orders, either for a specific Digital Asset or on the entire trading platform.
1.16 CASP means a crypto-asset service provider as defined in MiCA.
1.17 CLOB means central limit order book.
1.18 Corporate Participant is a Participant as referred to Section 4.4 of these Trading Rules.
1.19 Digital Asset has the meaning given thereto in the User Agreement.
1.20 EBA means European Banking Authority.
1.21 EEA means European Economic Area.
1.22 Fee means any charge or cost imposed by Bitvavo or an Affiliate, as applicable) on an Issuer or a Participant for the execution of transactions, provision of Services, or maintenance of an Account, admission to trading or otherwise.
1.23 Funds has the meaning given thereto in the User Agreement.
1.24 Halted means the status of the Bitvavo Trading Platform whereby there is a temporary suspension of trading activity, either for a specific Digital Asset or on the entire trading platform.
1.25 High Frequency Trading means an infrastructure intended to minimise network and other types of latencies that enable Algorithmic Trading at high speed.
1.26 Issuer means issuer as defined in MiCA.
1.27 Limit Order means an Order as described in Section 6.1(a)(ii) of these Trading Rules.
1.28 Market Maker means a Participant as referred to in Section 4.5 of these Trading Rules.
1.29 Market Order means an Order as described in Section 6.1(a)(i) of these Trading Rules.
1.30 Market Specification means the document that describes the attributes of a specific Digital Asset as defined in Section 5.7 of these Trading Rules.
1.31 MiCA means Regulation (EU) 2023/1114 on markets in crypto-assets, as amended or supplemented from time to time.
1.32 Order means an instruction to buy or sell Digital Assets on the Bitvavo Trading Platform.
1.33 Order Book means a digital ledger maintained by Bitvavo that records all buy and sell orders for a specific cryptocurrency pair.
1.34 Participant means any natural person or legal entity that engages in trading activities on the Bitvavo Trading Platform.
1.35 Price Guarantee Service means the price guarantee service, which is a service provided by Bitvavo that protects the Participant against price fluctuations in a specific Digital Asset for a pre-defined period of time.
1.36 Reference Price has the meaning given thereto in Section 6.3 (f) of these Trading Rules.
1.37 RfQ means Request for Quote.
1.38 RfQ Segment means the segment of the Bitvavo Trading Platform where Orders of the Participants opted in for Price Guarantee Services are routed pursuant to these Trading Rules.
1.39 Retail Participant is a Participant as referred to in Section 4.3 of these Trading Rules.
1.40 Services has the meaning given thereto in the User Agreement.
1.41 Stop Loss Order means an Order as described in Section 6.1(b)(i) of these Trading Rules.
1.42 Stop Loss Limit Order means an Order as described in Section 6.1(b)(ii) of these Trading Rules.
1.43 Take Profit Order means an Order as described in Section 6.1(b)(iii) of these Trading Rules.
1.44 Take Profit Limit Order means an Order as described in Section 6.1(b)(iv) of these Trading Rules.
1.45 Tick Size means the minimum price increment between two valid order prices for a market. Orders must be priced in multiples of the configured tick size.
1.46 Trading Bots means any automated software, script, algorithm, or service - proprietary or third-party - that accesses the Bitvavo Trading Platform via APIs to submit, modify, or cancel Orders, or to make trading decisions without a human initiating each action.
1.47 Trading Rules means these trading rules.
1.48 US Person means a United States citizen or resident individual, a partnership or corporation organized in the United States or under the laws of the United States or any State thereof, a trust if (i) a court within the United States would have authority under applicable law to render orders or judgments concerning substantially all issues regarding administration of the trust, and (ii) one or more U.S. persons have the authority to control all substantial decisions of the trust, or an estate of a decedent that is a citizen or resident of the United States, a branch or an agency of a foreign entity which is located in the U.S, or any non-discretionary or similar account (other than an estate or trust) held by a dealer or other fiduciary for the account or benefit of a U.S person, or any discretionary account or similar account (other than an estate or trust) held by a dealer or other fiduciary organized, incorporated, or (if an individual) resident in the United States
1.49 User Agreement means the contractual agreement between the Participant, Bitvavo, Bitvavo Custody B.V. which defines and governs the provision of the Services by the relevant entities and the use of the Services by Participants.
1.50 Website has the meaning given thereto in the User Agreement.
Any capitalized term not defined in these Trading Rules shall have the meanings given to them in the User Agreement.
2.1 The Bitvavo Trading Platform
Bitvavo operates a trading platform which manages several trading systems such as the CLOB segment and the RfQ segment, where Digital Assets can be purchased or sold, resulting in the exchange of Funds for Digital Assets and Digital Assets for other Digital Assets (āthe Bitvavo Trading Platformā).
These Trading Rules govern terms applicable to the trading on Bitvavo Trading Platform, ensure compliance with Article 76 MiCA and promote fair, efficient and transparent trading on the Bitvavo Trading Platform.
2.2 Licence
Bitvavo is licensed by the AFM under the registration number 41000010, as a CASP under MiCA and is permitted to provide the Digital Asset service of operation of a trading platform for crypto assets, custody and administration of crypto assets and transfer services for crypto assets. These Services are available in all EEA jurisdictions.
Bitvavo reserves the right to not make the Bitvavo Trading Platform available in all markets or jurisdictions where it is authorized or permitted to provide its Services, and may restrict or prohibit the use of the Bitvavo Trading Platform by residents of certain jurisdictions.
For the avoidance of doubt, Lending Services are provided by Bitvavo Custody B.V. solely and Bitvavo Custody B.V is not subject to the supervision of the AFM.
Staking Services, Lending Services, Margin Trading Facility and Price Guarantee Services are not services regulated under MICA and involve certain risks, while using these services you may not be subject to the safeguards and protections under MICA.
3.1 Requirements for (Issuers of) Digital Assets seeking admission to trading at Bitvavo
(a) Bitvavo has implemented a Digital Asset admission processĀ based on which Bitvavo determines whether a new Digital Asset can be admitted to trading on the Bitvavo Trading Platform. Bitvavo may in its sole discretion determine whether or not a Digital Asset can be admitted to trading on the Bitvavo Trading Platform.
(b) Each Digital Asset to be admitted to trading on the Bitvavo Trading Platform should meet and continue to meet requirements on its business case, feasibility, compliance, legal, risk and suitability requirements as set by Bitvavo from time to time.
3.2 Application procedure for admission to trading at Bitvavo
The application procedure will be carried out in accordance with Bitvavoās policies and procedures. In summary, Bitvavo considers the following criteria:
(a) a business case assessment (including market viability and economic and strategic fundamentals) and pre-scan (for the feasibility and compliance assessment);
(b) a feasibility assessment (including custody, liquidity and blockchain integration);
(c) a compliance, legal and risk assessment (compliance with applicable laws, KYC, customer due diligence assessments proportionate to the risk profile of the applicant, audit and privacy and the risks associated with the Digital Asset);
(d) a suitability assessment (asset value, security, technology and additional risk and compliance requirements); and
(e) admission to go-live preparation (date, technological preparation, liquidity, inventory, and communication).
3.3 Conditions for Digital Assets to remain admitted to trading
(a) Liquidity thresholds
To remain eligible for trading, each Digital Asset that is admitted to trading on the Bitvavo Trading Platform must consistently achieve a daily average transaction volume that meets or exceeds the threshold periodically set by Bitvavo.
(b) Disclosure requirements
To remain eligible for trading, Issuers of Digital Assets must at minimum disclose the following information on their website:
(i) a Digital Asset whitepaper in compliance with the requirements in MiCA, if applicable; and
(ii) whenever there is a significant new factor, material mistake or material inaccuracy that can affect the assessment of the Digital Assets, the modified Digital Asset whitepaper, including the reasons for such modification, in accordance with MiCA, if applicable.
3.4 Ongoing monitoring of Issuers and Digital Assets
(a) To ensure continued credibility, security and efficiency of its markets and the Digital Assets that are admitted to trading and their compliance with this Section 3 of the Trading Rules, BitvavoĀ continuously monitors applicable risk factors that would possibly lead to a trading suspension or a delisting of any admitted Digital Assets. To perform this ongoing monitoring, Bitvavo leverages automated alerts and tooling that may prompt re-evaluations of Digital Assets admitted to trading, taking into account developments in the Digital Assets market, including regulatory changes, technological issues or changes, market dynamics, liquidity and concentration of the Digital Assets.
(b) With regard to liquidity, Bitvavo assesses whether the liquidity provided by Market Makers to the Order Book is appropriately aligned with the Order volumes in the Order Book. Bitvavo also assesses the trading activity in the relevant Digital Asset on other Digital Asset trading platforms.
3.5 Digital Assets Not Admitted to Trading at the Bitvavo Trading Platform
A Digital Asset is not admitted to trading on the Bitvavo Trading Platform if:
(a) it does not pass the application procedure as referred to in Section 3.2 of these Trading Rules;
(b) no corresponding Digital Asset white paper has been published in the cases required by MiCA; or
(c) it has an inbuilt anonymization function, unless the holders and transaction history can be identified by Bitvavo.
4.1 Participant criteria
A person can be a Participant of the Bitvavo Trading Platform if:
(a) the person has created an Account as set out in the User Agreement;
(b) the person has accepted the User Agreement and these Trading Rules.
(c) the person complies with mandatory regulatory obligations related to Market Abuse prevention, AML/CFT/PSE rules and regulatory licensing requirements (if applicable) at Bitvavoās sole discretion; and
(d) Bitvavo has accepted this person as a Participant.
4.2 Participant categories
Bitvavo distinguishes four categories of Participants:
(a) Retail Participants;
(b) Corporate Participants;
(c) Market Makers; and
(d) Brokers (including, but not limited to, providers of trading bots or other services through the Bitvavo API).
4.3 Retail Participants
A Retail Participant can be a natural person that is at least 18 years old, that is not a US Person and that is resident in a jurisdiction in the EEA where Bitvavo Services are available.
4.4 Corporate Participants
A Corporate Participant can be a legal entity that is not a Market Maker or a Broker and that is resident or established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its Services.
4.5 Market Makers
A Market Maker can be a natural person or legal entity that has entered into a market making agreement with Bitvavo and that complies with the terms thereof, the User Agreement and any other agreement concluded with Bitvavo or Bitvavo Custody. A market making agreement includes specific terms and conditions to obtain access to the Bitvavo Trading Platform as a Marker Maker, such as, amongst others, the Digital Assets covered by the market making agreement, minimum up-times and response times, the streaming of prices/quotes on both sides of the market, spread limits, fees, credit lines, incentives and penalties for non-compliance.
4.6 Brokers
A Broker can be a legal entity that is a resident or is established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its services, and, if applicable, is authorised to provide crypto-asset services as defined in MiCA, and that complies with the terms of any agreement with Bitvavo. A Broker operating one or more Trading Bots that wants to access the Bitvavo Trading Platform must agree to the Bitvavo Developer Agreement and/or the API Partner Agreement.
4.7 Trading limits
(a) Bitvavo applies trading limits to the Account of Participants, including daily, weekly, monthly, annually and total limits. Bitvavo may set such limits in its sole discretion, based on the information provided by Participant and any other information available to Bitvavo (including, but not limited to, the Account balance of the Participant, the trading behaviour of the Participant, the capacity and resilience of the Bitvavo Trading Platform and the market for each relevant Digital Asset).
(b) Bitvavo may include the different trading limit thresholds as an indication on its Website. Bitvavo can amend the procedures and limits from time to time without prior notice and with immediate effect.
(c) Bitvavo may require a Participant to provide or verify additional information, or to wait some period of time after execution of a trade or a transaction, before settlement of such trade and before permitting a Participant to enter into any subsequent trades on the Bitvavo Trading Platform.
(d) A Participant may submit a request for higher limits. Bitvavo may require the Participant to submit additional documentation in this regard and does not guarantee that limits will be raised as requested.
5.1 Trading Days and Trading Hours
The Bitvavo Trading Platform is available for trading every day, 24 hours per day, except for scheduled or unscheduled down-time. Specific trading conditions may apply from time to time, for all admitted Digital Assets or on an asset-by-asset basis, for example during a specific status as determined by Bitvavo, including Halted markets, Cancel Only markets or during Auction periods, as set out in these Trading Rules.
5.2 Transactions
(a) Participants can submit instructions to buy or sell Digital Assets on the Bitvavo Trading Platform (placing an Order), against other Digital Assets or Funds where pairs are offered by Bitvavo from time to time (geographical restrictions may apply).
(b) Bitvavo is not a Participant and Bitvavo will not act as a counterparty of a Participant in any transaction in Digital Assets executed on the Bitvavo Trading Platform.
(c) The Participant is solely responsible for placing Orders and providing any other instructions.
(d) Bitvavo or other Participants may provide information on Digital Assets, including, but not limited to, the price and volatility. This information as well as any other information on the Bitvavo Trading Platform does not constitute investment advice, a recommendation to sell or buy or an opinion of Bitvavo.
(e) The price indicated on the transaction confirmation is the price at which an Order has been executed. This price may deviate from prices indicated or referenced on the Bitvavo Trading Platform prior to the execution of an Order. The price indicated on the transaction confirmation is always conclusive over other price indications.
5.3 Recurring Buy
(a) Participants can automatically buy selected Digital Assets on a monthly basis by switching on the āRecurring Buyā feature.
(b) By using this feature, Participants authorise Bitvavo to deduct Funds and Fees directly from their Account at a random timestamp on a certain day of each month as selected by the Participant.
5.4 Holding of Funds
Once an Order to buy Digital Assets is placed, a certain amount of Funds is placed on hold in the Participantās Account. This means that these Funds can only be used to fulfil the Order for which they are reserved. The amount of Funds that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Funds on hold accordingly.
5.5 Holding of Digital Assets
Once an Order to sell Digital Assets is placed, a certain amount of Digital Assets is placed on hold in the Participantās Account. This means that these Digital Assets can only be used to fulfil the Order for which they are reserved. The amount of Digital Assets that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Digital Assets on hold accordingly.
5.6 Orders and Market Segments
(a) If a Participant has enabled the Price Guarantee Service, Orders that are eligible for Price Guarantee Service that are submitted by the Participant are considered an RfQ (Request for Quote) and will be routed to the RfQ Segment.
(b) All other Orders will be routed to the CLOB segment.
(c) Bitvavo has the sole discretion to decide on which market segment a Digital Asset may be traded and may require certain Digital Assets to be traded on an RfQ-only basis where the liquidity of certain Digital Assets changes.
(d) Bitvavo has the sole discretion to form different market segments, define and change terms applicable to such market segments.
5.7 Market Specifications
(a) Bitvavo will publish Market Specifications detailing the terms of any Digital Assets admitted to trading on the Bitvavo Trading Platform.
(b) Bitvavo may amend, at its sole discretion, the Market Specifications and such amendments shall be communicated to Participants on reasonable notice.
5.8 Cancellation of transactions
5.8.1 Bitvavo may, in its sole discretion, or following a request by a Participant, conduct a review of a transaction executed on the Bitvavo Trading Platform where (i) there is a reasonable basis to believe that such transaction has been executed as a result of an erroneously submitted Order, or (ii) executed in violation of applicable laws and regulations (including market abuse) and these Trading Rules, (iii) or where so requested by competent authorities or courts.
5.8.2. Bitvavo shall notify the relevant Participants to a transaction of the result of an investigation into one or more transactions.
5.8.3. If Bitvavo, at its sole discretion, determines the transaction subject to an investigation is clearly erroneous or executed in violation of applicable laws and regulations (including market abuse) and these Trading Rules, or if requested by competent authorities or courts, it may nullify the transaction, un-wind the fund movements resulting from the transaction and shall notify the affected Participant(s) accordingly.
6.1 Order Options
(a) The main Order options available on the Bitvavo Trading Platform are a Market Order or a Limit Order.
(i) Market Order:
(A) A Market Order is matched with the best-priced Limit Order in the Order Book at the time of the request. If there are more than one such Limit Orders, the Market Order is matched with the oldest one.
(B) There is no guarantee that a Market Order will fill at the market price indicated. A Market Order may fill at a number of different prices, based on the quantity of the Market Order and the quantities and direction of the existing Orders in the Order Book at the time.
(ii) Limit Order:
(A) A Limit Order is an Order to buy or sell at a fixed price.
(B) A Limit Order will be executed if or when the market price reaches the limit price and will be filled at the limit price or better.
(1) A buy Limit Order will be executed only at the limit price or a lower price.
(2) A sell Limit Order will be executed only at the limit price or a higher price.
(b) Additional advanced order options that may be available on the Bitvavo Trading Platform are Stop Loss Order, Stop Loss Limit Order, Take Profit Order, Take Profit Limit Order and One-Cancels-the-Other. The availability of these order options may depend on the method of access to the Bitvavo Trading Platform.
(i) Stop Loss Order:
(A) A Stop Loss Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches a specified trigger price in order to limit Participant losses.
(B) Once a Stop Loss Order has been placed, it is considered āactiveā until cancelled or until the relevant Market Order is placed, when the stop price has been triggered.
(C) A Stop Loss Order is not posted to the Order Book and is not visible to other Participants.
(ii) Stop Loss Limit Order:
(A) Stop Loss Limit Order mechanics are similar to Stop Loss Order with the main difference that Stop Loss Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
(iii) Take Profit Order:
(A) A Take Profit Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches the take profit price to realise Participant profits.
(B) Once a Take Profit Order has been placed, it is considered āactiveā until it is cancelled or until the relevant Market Order has been placed when the trigger price is reached.
(C) A Take Profit Order is not posted to the Order Book and is not visible to other Participants.
(iv) Take Profit Limit Order:
(A) Take Profit Limit Order mechanics are similar to Take Profit Order with the main difference that Take Profit Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
(v) One-Cancels-the-Other
(A) This Order type enables Participants to place two linked conditional Orders, (i) a Take Profit or a Take Profit Limit Order and (ii) a Stop Loss or a Stop Loss Limit Order where the triggering of one leg of the Order will result in the automatic cancellation of the other Order.
(B) In this Order type, both legs of the Order should be of the same direction i.e. sell side for both legs or buy side for both legs of the Order.
6.2 Submission and execution of Orders
(a) An Order is submitted by a Participant via the App, Website or API. The Participant selects the Digital Asset it wants to buy or sell and enters the Order details. Subsequently, the Participant submits the Order to the Order Book.
(b) Once the Order is submitted by the Participant and received by the Bitvavo Trading Platform system, Bitvavo performs a validation of the Order details, including if the Participantās balance is sufficient, the market protection checks as set out in Section 6.3 of these Trading Rules and whether, in Bitvavoās sole discretion, the Order contains all the relevant datapoints as pertaining to the Order, including datapoints that are required for Bitvavo to comply with applicable regulations or any other datapoints to be included in any Order. If the Order fails any of these checks, the Order is rejected and the Participant is notified. If the Order passes these checks, the Order is accepted by Bitvavo, entered into the Order Book and the Participant is notified.
(c) Once accepted into the Order Book, the Order is either matched with another existing Order in the Order Book with an opposite direction, or is added to the Order Book. If an Order is matched with another Order, this results in the execution of the Order in line with Section 6.5 - 6.8 of these Trading Rules. The Participant receives confirmation of such execution.
(d) An Order has the following parameters:
(i) Market: Name of the market, in the format BASE-QUOTE (e.g. BTC-EUR).
(ii) Side: Buy or sell.
(iii) Order Type: Limit Order or Market Order. When placing a Limit Order, the Order might still be executed against a better price than specified, in which case it is processed as a Market Order. There is also a possibility to submit advanced order types as described in Section 6.3.
(iv) Amount: The quantity of the base asset to be bought/sold (required for Limit Orders, optional for Market Orders). Applicable quantity decimal precisions are detailed in the relevant Market Specification.
(v) Amount Quote: The amount specified in the quote asset (optional for Market Orders, either Amount or Amount Quote is required)
(vi) Price: The price for base asset specified in the quote asset (required for Limit Orders). Applicable Tick Sizes are detailed in the relevant Market Specification.
(vii) Time In Force: This specifies how long the Order should be placed on the Order Book. This only applies to Limit Orders. The following options are allowed:
(A) GTC: Good-Til-Cancelled. This is the default setting and places an order on the Order Book until it is filled or cancelled.
(B) IOC: Immediate-Or-Cancel. This allows (partial) filling of the Order when it is submitted. The remaining amount that cannot be matched immediately will be cancelled.
(C) FOK: Fill-Or-Kill. This ensures that the entire Order is either filled or cancelled. Partial fills are not possible.
(viii) Self-Trade Prevention: Trading with oneself is not allowed. This setting handles what should be done if a Participantās Order would match with one of the Participantās own orders. The following options are allowed:
(A) Decrement And Cancel: This is the default setting and modifies both Orders by the amount that would have been filled. This results in the smaller of the two Orders being cancelled, and the other Order being reduced in size.
(B) Cancel Oldest: Cancels the oldest Order.
(C) Cancel Newest: Cancels the newest order.
(D) Cancel Both: Cancels both Orders.
(ix) Post Only: Limit Orders that have this set to true will be cancelled if matched immediately. This ensures that the Participant pays the maker fee and not the taker fee. As a default, Post Only is switched off.
(x) Response Required: If this value is set to false, only the Order ID of the newly created Order is returned. The default value is true (i.e. a full response).
6.3 Market Protections
(a) Order Minimums/Maximums
All Market Orders, Limit Orders, and Stop OrdersĀ placed on the Bitvavo Trading Platform are subject to minimum and maximum Order Amount and Amount Quote requirements per market.
(b) Number of Open Orders
All Participants are subject to a maximum number of Orders that may be open in the Order Book per market. When a Participant reaches the limit in a given market, any Orders entered in that market thereafter are rejected until the number of open Orders stored in the Order Book for the given market decreases below the limit.
(c) Placement Price Protection
Limit Orders with a Good-Til-Cancelled Time in Force are subject to a Placement Price Protection. Buy (Sell) Limit Orders with a price lower (higher) than the lower (upper) Placement Price Protection Band will be rejected.
(i) The Upper Placement Price Protection Band is calculated by multiplying the Placement Price Multiplier times the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed.
(ii) The Lower Placement Price Protection Band is calculated by dividing the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed by the Placement Price Multiplier.
(d) Execution Price Protection
Limit Orders are subject to an Execution Price Protection. Buy (Sell) Limit Orders with a price higher (lower) than the upper (lower) Execution Price Protection Band will be rejected.
(i) The Upper Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed plus the Execution Protection Threshold percentage.
(ii) The Lower Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed minus the Execution Protection Threshold percentage.
(e) Spread Price Protection
(i) Market Orders are subject to a Spread Price Protection. Market Orders will fill at prices up to the Spread Protection Threshold from the mid-point price between the best bid and best offer on the Order Book at the time the Market Order is placed. If a Market Order would fill against Orders beyond the Spread Protection Threshold, the Order will partially fill up to the Spread Protection Threshold level and all the remaining quantity of the Order will be cancelled.
(f) Reference Price Protection
All Orders are subject to Reference Price Protection, which limits how far the price at which an Order is executed, can deviate from the market price at the time the Order is placed (the āReference Priceā).
The Reference Price is an index price, calculated using price data from multiple external exchanges to reflect a fair market value for the Digital Asset. Orders will only be filled at prices within what is known as the āReference Price Protection Thresholdā, which is a defined range from this Reference Price. If the price at which an Order would be filled falls outside this threshold, only the portion of the Order within the threshold will be filled; the rest will be cancelled. This may result in some Orders being partially filled.
If a valid reference price is unavailable, or if Bitvavo determines that the index does not accurately represent current market conditions, this protection will not apply.
(g) Cancel on Disconnect
Cancel on Disconnect is a risk management feature that automatically triggers a cancellation of all open Orders placed by a Participant if there is a loss of connection to the Trading Platform for a period specified by the Participant.
Participants can group certain Digital Assets whereby each group would be subject to a different inactivity period after which open Orders in all Digital Assets in such group will be automatically cancelled.
This feature is available to Participants who opt-in for this feature. Bitvavo reserves the right to make this function available to only advanced Participants. Cancellation of open Orders will be processed within the general rules applicable to cancellation, Bitvavo does not guarantee automatic or immediate cancellation.
(h) General note for this section
The limits, multipliers and thresholds used for this section 6.3 shall be determined by Bitvavo for each market.
6.4 Errors
(a) In exceptional cases, there may be errors in the Bitvavo Trading Platform, including in relation to the prices displayed or the way in which Orders are matched. In addition, the Digital Assets on the Bitvavo Trading Platform may be subject to unusual price movements, including as a result of market manipulation or sudden drops or spikes in liquidity. In such cases, Bitvavo may at its sole discretion (and is in no way obliged to):
(i) retrospectively correct any such errors or rectify any such price movements, including by amending or reverting transactions, which may be to the advantage or to the disadvantage of Participant; or
(ii) temporarily or indefinitely halt trading on the Bitvavo Trading Platform for one or more Digital Assets;
(b) Especially during periods of high volume, illiquidity, fast movement or volatility, any Digital Assets traded on the Bitvavo Trading Platform may be executed at a different rate than displayed to the Participant at the time of Participants Order.
(c) Ā In the case of suspected fraud or misuse, Bitvavo reserves the right to suspend or cancel Orders and transactions until the legitimacy has been verified.
6.5 Order Matching and Execution During Regular Trading
(a) Orders that are matched immediately are taker orders. Orders that are not matched immediately and are placed in the Order Book are maker orders.
(b) Limit Orders may be maker or taker orders, depending on whether the Limit Order can be matched immediately. If matched immediately, the Limit order is a taker order. If placed on the Order Book, the Limit Order is a maker order.
(c) Orders are matched based on price-time priority. This means that taker Orders are matched with the maker Orders with the best available price. If several Orders have the same price, the oldest maker Order is matched. This process continues until the Order is filled, placed on the Order Book, or cancelled.
(d) The price paid/received is determined by the maker order. This means that Limit Orders can be filled at prices better than their limit price.
(e) Fills may be settled nearly instantly or after a period of time.
(f) The execution price of a Market Order may differ significantly from the indicated price. This may be due to a change in price between the time of the Order being initiated by the Participant and the execution of the Order (i.e. 'slippage').
(g) Market Orders, Limit Orders, and stop Limit Orders are not guaranteed executable due to the required availability of sufficient supply or demand.
(h) Orders may be executed instantly or after a period of time and will be considered to have taken place at the execution date and time.
6.6 Order Matching During Halted Markets
(a) Bitvavo may, in its discretion, temporarily halt trading in a market to preserve market integrity, orderly trading conditions, and/or to conduct regular scheduled maintenance.
(b) Orders cannot be placed, modified or cancelled when a market is Halted.
(c) No order matching occurs when a market is Halted.
(d) No Order Book updates will be broadcasted when a market is Halted.
6.7 Order Matching During Cancel Only Markets
(a) Bitvavo may, in its sole discretion, temporarily set Cancel Only in a market to preserve market integrity and/or to conduct regular scheduled maintenance.
(b) Orders can be cancelled when a market is in Cancel Only status.
(c) Orders cannot be placed or modified when a market is in Cancel Only status.
(d) No order matching occurs when a market is in Cancel Only status.
6.8 Order Matching During Auctions
(a) Bitvavo employs an Auction methodology after a market has been Halted or put into Cancel Only before Regular Trading resumes to guarantee price discovery and orderly markets.
(b) The Auction process consists of two phases:
(i) Auction Collection:
(A) A Participant cannot place a Market Order when a market is at the Auction Collection phase.
(B) A Participant can place, modify or cancel all other Order types when a market is at an Auction Collection phase.
(C) No Orders will be matched during the Auction Collection.
(ii) Auction Matching:
(A) A Participant cannot place, modify or cancel Orders when a market is at the Auction Matching phase.
(B) During this period, Orders will be matched in accordance with the procedure as set out below.
(C) Active Limit Orders are used to determine the price at which the most units of the base asset are traded. If there is no price where trades occur, no matching occurs and Regular Trading resumes.
(D) If a price is obtained in the previous step, this price is used to prevent self-trades (according to the specifications made by the User regarding the treatment of its Orders for self trade prevention).
(E) Orders are matched based on price-time priority and all Orders are considered taker orders. Limit Orders with the best price will be filled first, at the price determined in step (1).
(F) When no more Limit Orders can be matched at the determined price, Buy Post-Only Orders with a price above the determined price and Sell Post-Only Orders with a price below the determined price are cancelled and Regular Trading resumes.
(c) No Order Book updates will be broadcasted when a market is at Auction phase.
7.1 Price Guarantee Service
The Price Guarantee Service protects the Participant against price fluctuations in a specific Digital Asset for a period of 5 seconds upon submission of the Order. This market risk is absorbed by the Participant interacting on the RfQ Segment and responding to RfQ. To account for the market risk taken by the Participant between the time of the Participantās quote and the execution of the Order, each quote may include a compensation (spread).
7.2 Price Guarantee Trades
(a) An Order via the Price Guarantee Service will result in a trade when the Participant has accepted the quote that has been shown to it in response to the opening of the order form and the entering of the relevant details of the order by the Participant.
(b) If a quote under the RFQ Segment is accepted in a timely manner by a Participant, the RfQ will be executed under the Price Guarantee Service terms set out herein, and such RfQ will be deemed a taker order of that Participant.
7.3 Price Guarantee Quoting Process
If a quote is not accepted by a Participant within five (5) seconds, the quote will be refreshed with a new quote, which will again be valid for five (5) seconds. This process is repeated until a Participant accepts a quote, which will result in a (partial or entire) execution of the PG Order. Alternatively, the process ends when a Participant does not accept a quote and exits the order form for a specific crypto pair. If there are no available quotes on the RFQ Segment then the Participant will be prompted to execute a standard Market Order.
7.4 Quotes on the RFQ Segment
Prices of the quotes provided by Participants interacting on the RfQ Segment in response to RfQ must remain within a predetermined range. Only quotes that fall within this range will be considered by Bitvavoās matching engine in selecting the best quote (best from the Participant's perspective) that will be displayed to the Participant in response to a given RfQ .
7.5 Algorithmic Trading
Participants may engage in Algorithmic Trading on the Bitvavo Trading Platform provided that:
(a) the Participant has given prior notice to Bitvavo each time it wishes to deploy a new algorithm or a material change to an algorithm on the Bitvavo Trading Platform and provide a description of the algorithm including a unique identification number assigned to such algorithm, which shall be included in any order or quote generated or governed by such algorithm. Participant shall update such details and identification number upon each material change of the algorithm;
(b) prior to deployment of any algorithm on the Bitvavo Trading Platform, the Participant has performed appropriate and successful testing of each algorithm ensuring an algorithm does not contribute to or create disorderly market conditions on the Bitvavo Trading Platform;
(c) upon Bitvavoās instruction, the Participant shall use the testing environment made available by Bitvavo for purposes of conformance testing any new algorithm or substantial change to an algorithm, prior to deployment on the Bitvavo Trading Platform;
(d) each algorithm on the Bitvavo Trading Platform shall comply with Bitvavoās Trading Rules and applicable regulations;
(e) upon Bitvavoās request, the Participant shall provide certification in writing of the successful testing for each algorithm to be deployed on the Bitvavo Trading Platform, including for each substantial change thereto prior to the deployment on the Bitvavo Trading Platform;
(f) each of their algorithms deployed on the Bitvavo Trading Platform is continuously monitored by the Participant to prevent disorderly trading.
(g) the participant complies with all applicable regulatory obligations, including those relating to the prevention of market abuse, money laundering, terrorism financing, sanctions, and any relevant licensing or authorisation requirements.
7.6 Conditions to High Frequency Trading
Bitvavo may, in its sole discretion, apply conditions to the deployment of High Frequency Trading techniques on the Bitvavo Trading Platform.
7.7. Margin Trading
7.7.1 Margin Trading is a trading strategy that allows a Participant to borrow Digital Assets (āMargin Tradingā). A Participant may open a short position by borrowing a Digital Asset and then selling Digital Assets with the intention of buying them back later at a more favorable price.
7.7.2 Bitvavo may allow Participants to engage in Margin Trading on Bitvavo Platform. Margin Trading Facility offered to Participants will allow Participants to take a short position or multiple short positions in a Digital Asset by borrowing such Digital Assets from Bitvavo Custody (āBorrowed Assetsā) in exchange for collateral (āMargin Trading Facilityā).
7.7.3 The Participant could trade on margin by using the Margin Account. The Participant shall monitor each Margin Position, the Borrowed Assets and corresponding Margin Collateral in its Margin Account.
7.7.4 The Participant shall monitor the Health Ratio at all times to avoid Liquidation of the relevant Margin Position. If the Liquidation is triggered, Margin Collateral will be used to recover Borrowed Assets, Borrowing Fee and Liquidation Fee.
7.7.5. The Participant acknowledges and agrees that Liquidation may occur automatically, without prior notice, and irrespective of whether other rights or remedies under these Trading Rules and the User Agreement (including provisions relating to default, Force Majeure, or insolvency) have been exercised.
8.1 Grounds for Suspension
Bitvavo may, in its sole discretion, suspend or remove one or more Digital Assets or Participants from trading or to suspend trading on the Bitvavo Platform in its entirety or for an individual Participant. Among others, Bitvavo can do so in the following circumstances:
(a) to prevent disorderly market conditions;
(b) upon the substantiated request of an Issuer;
(c) in case of (suspected) fraud, deception or market abuse;
(d) failure of an Issuer or a Participant to comply with these Trading Rules;
(e) failure of an Issuer or a Participant to comply with applicable legislation;
(f) in case of bankruptcy of an Issuer or a Participant;
(g) failure of an Issuer or a Participant to provide requested information to Bitvavo, or a supervisory authority;
(h) in case of technical or operational disruption;
(i) in case of the occurrence of events in the financial markets or the Digital Asset markets that may have material adverse effect on the orderly trading, integrity or resilience of the Bitvavo Trading Platform; or
(j) if deemed appropriate by Bitvavo in its sole discretion in order to protect the integrity or resilience of the Bitvavo Trading Platform, or to protect the interests of any Participant, Bitvavo or any Affiliate of Bitvavo.
8.2 Request from Supervisory Authority
Bitvavo will comply with a request of a supervisory authority to suspend or prohibit trading as referred to in Section 16 of these Trading Rules.
8.3 Suspension of Trading for Maintenance
Bitvavo may temporarily suspend trading for maintenance or for other reasons. Generally, Bitvavo will proceed according to the following steps:
(a) Announcement scheduled downtime: Participants will be informed through a message on account.bitvavo.com.
(b) Scheduled downtime begins: Participants will be informed through a message on account.bitvavo.com.
(c) Scheduled downtime ends: Markets will be placed in Halted mode. Participants will be informed through a message on account.bitvavo.com when trading resumes. This will be at least 15 minutes after the scheduled downtime ends.
8.4 Market Status During and After Suspension
During a suspension, the Bitvavo Trading Platform will be placed in Halted mode. When trading resumes after a suspension, Bitvavo will apply the Auction methodology as referred to in Section 6.8 of these Trading Rules.
9.1 Settlement of Digital Assets
Bitvavo is responsible for the correct execution and settlement of the purchase and sale of Digital Assets on the Bitvavo Trading Platform in accordance with applicable regulations.
9.2 Off-Chain Settlement
All transactions on the Bitvavo Trading Platform are settled off-chain. Final settlement is generally initiated immediately or shortly after execution of a transaction on the Bitvavo Trading Platform and by the end of the Trading Day at the latest. The settlement process results in the transfer of rights associated with the traded Digital Assets from one Participant to another against the payment of the transaction price, while the Digital Assets themselves continue to be held by the Foundation, but on behalf of the acquiring Participant.
10.1 Pre-Trade Transparency
Bitvavo publishes the bid and ask prices and the depth of trading interest at those prices which are advertised on the Bitvavo Trading Platform for Digital Assets in accordance with applicable regulations. Bitvavo makes this information available on a continuous basis on its website.
10.2 Post-Trade Transparency
Bitvavo publishes the price, volume and time of the transactions executed in respect of Digital Assets traded on the Bitvavo Trading Platform in accordance with applicable regulations. Bitvavo publishes this information as close to real-time as technically possible in the App and on the Website.
10.3 Access to this Information
Bitvavo makes available the information in this section on a non-discriminatory basis. The regulatory information will be made available free of charge 15 minutes after publication in a machine-readable format, and it will remain published for at least two years.
11.1 Modification and Termination of Trading
Bitvavo may, in its sole discretion, for any reason and without liability to Participant, (i)Ā modify, discontinue or terminate, temporarily or permanently, part or all of its trading services in general, and (ii) suspend, restrict or terminate Participantās access to the Bitvavo Trading Platform.
11.2 Bitvavo Trading Platform Availability
All Services are provided on an āas isā and āas availableā basis without warranty of any kind. Bitvavo does not guarantee that the Bitvavo Trading Platform will be available for any absolute or relative amount of time. Bitvavo does not warrant that access will not be interrupted or that there will be no delays, failures, errors, loss or similar of transmitted information. This may include, but is not limited to, unavailability of any of the Services during times of high volume, illiquidity, fast movement or volatility.
11.3 No Obligation to Provide Services
Bitvavo has no obligation to make available the Bitvavo Trading Platform to anyone when Bitvavo may reasonably believe that this would violate applicable laws and regulations.
12.1 Access to Bitvavo Trading Platform via API
Bitvavo may provide access to Participants to the Bitvavo Trading Platform and specific data and information through an āApplication Programming Interfaceā (API) which may be subject to additional terms and conditions as set by Bitvavo from time to time.
12.2 Use of API
To use the API, one or more API key(s) with corresponding secrets (API Credentials) must be created. The Participant is solely responsible for safeguarding the API Credentials and for any activities by the Participant or third parties that have access to the Account, whether authorized or not. In the event that the Participant knows, or should know, that API Credentials have been stolen or misused, the Participant shall contact Bitvavo immediately.
12.3 Changes to API
Bitvavo may, in its sole discretion, add, discontinue or remove, in whole or in part, the API at any time and without notice. Bitvavo cannot guarantee that future versions of the API will be backwards compatible. Participant acknowledges and understands that any of these changes may adversely affect Participantās use of the API and might require the Participant to make substantial changes in order to continue using the API, and that this is the Participantās own responsibility.
12.4 API Scope and Modifications
The scope and concrete form of the API is at Bitvavoās sole discretion. The API may be modified or abandoned at Bitvavoās sole discretion.
12.5 Monitoring of API use
Bitvavo may monitor the use of the API. The Participant will not block or otherwise interfere with the monitoring process.
12.6 API Limits
Bitvavo may set limits on the number of messages or Orders that the Participant can transmit through the API or extend limits for other Participants, in its sole discretion, during any given period and without notice. The Participant shall not attempt to circumvent such limitations. If the Participant exceeds the limits, Bitvavo may moderate the Participant activities, may cease offering access to the API or may immediately suspend or terminate access to the API in its sole discretion and without notice.
12.7 Prohibited Use of the API
The Participant shall not, and shall not encourage or authorize others to:
(a) use the API in any manner that is not expressly authorized by the User Agreement and the Trading Rules;
(b) alter, reproduce, adapt, distribute, display, publish, reverse engineer, translate, disassemble, decompile or otherwise attempt to create any source code that is derived from the API;
(c) use or access the API for purposes of monitoring the availability, performance, or functionality of any of the Services or for any other benchmarking or competitive purposes;
(d) collect, cache, aggregate, or store data or content accessed via the API other than for purposes allowed under the User Agreement;
(e) use the API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise impacts the stability of Bitvavoās servers or impacts the behaviour of other applications using the API;
(f) attempt to cloak or conceal Participantās identity when requesting authorization to the API;
(g) use the API to (i) access or use any information not permitted by the User Agreement and these Trading Rules, to (ii) circumvent or break any of Bitvavoās administrative, technical or organizational security measures, (iii) disrupt, impair, overburden or degrade the API or the Services, (iv) change the API or the Services in any way, or (v) test the vulnerabilities of the Services or API; and
(h) use any data collected from Participantās use of API for advertising purposes.
13.1 Access to Market Data
All Participants have full and equal real-time access to market data. Market data is made available through the web interfaces and Bitvavo API.
13.2 Equal Opportunity
All Participants have equal opportunity with regard to access the web interfaces and Bitvavo API.
14.1 Market Abuse
Participants are prohibited from engaging in market abuse, including insider dealing and market manipulation as referred to in Title VI MiCA.
14.2 Market Abuse - Prohibited Activities
Without prejudice to the prohibitions as set out in Title VI MiCA, Participants are prohibited from any behaviour that may constitute market abuse, including but not limited to carrying out the following activities on the Bitvavo Trading Platform:
(a) Pump and dumps: artificially inflating the price of a Digital Asset through false and misleading positive statements, in order to sell the cheaply purchased Digital Asset at a higher price.
(b) Wash trading: Simultaneously buying and selling the same Digital Assets to create false trading volume and artificially inflate market activity.
(c) Front-running: Trading in advance of a large client order to take advantage of anticipated price movements resulting from the execution of that order. Front running involves using non-public information about future or pending transactions for their own benefit.
(d) Churning: excessive trading activity by (Broker) Participants on behalf of their clients, on either side of the Order Book, intended to increase the Participantās (Broker) commissions.
(e) Quote stuffing: quickly entering and then withdrawing large orders in an attempt to flood the market with quotes, causing competitors to lose time in processing them or causing other disorderly trading conditions.
(f) Spoofing / layering: creating the illusion of pessimism (or optimism) in the market by placing buy or sell orders without the intention of filling them.
(g) Insider trading: trading in Digital Assets based on non-public information that could affect the price of those Digital Assets.
(h) Information-based market abuse: spreading false or misleading information about crypto companies, crypto projects, Digital Assets, or market conditions to influence prices or trading activity. This includes disseminating rumours, false news, or deceptive market commentary to manipulate market participants perceptions.
(i) Improper disclosure practices: failing to disclose non-public information that could affect market prices or engaging in selective disclosure of information to certain market participants. Misleading disclosures or inadequate transparency about financial performance, risks, or other material matters related to a Digital Asset can also constitute market abuse.
14.3 Prohibition to Use the Account and the Services for Criminal Activities
A Participant may not use the Account and the Services to perform criminal activities of any sort, including but not limited to money laundering, terrorist financing, sanction evasion, fraud or any other criminal or illegal activity, the existence whereof is to be determined by Bitvavo at its sole discretion. These include, but are not limited to, the following:
(a) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to sanctions programs administered in the countries where Bitvavo conducts business, including but not limited to the EU Sanctions list.
(b) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to terrorist financing as applicable in the countries where Bitvavo conducts business.
(c) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to money laundering as applicable in the countries where Bitvavo conducts business.
(d) Activity which would be related to fraud such as activities which operate to defraud Bitvavo (including Participants providing any false, inaccurate, or misleading information to Bitvavo), Participants and/or other persons.
(e) Activity which would be related to drugs such as sale of narcotics, controlled substances, and any equipment designed for making or using drugs.
(f) Activity which would be related to multi-level marketing such as pyramid schemes and network marketing.
(g) Activity which would be related to unfair, predatory or deceptive practices such as investment opportunities or other services that promise (too) high rewards and sites that Bitvavo determines in its sole discretion to be unfair, deceptive, or predatory towards Participants.
(h) Activity which would be related to illegal gambling such as unregulated lotteries, sports forecasting or odds making and comparable activities.
(i) Activity which would be related to high-risk businesses such as any businesses that Bitvavo believes to pose elevated financial risk, legal liability, or violates bank policies.
(j) Activity which would be related to (attempts to) to reverse engineer, modify, translate or disassemble the (software behind the) Bitvavo Environment in whole or in part.
14.4 Reporting to the AFM
Bitvavo will report to the AFM if it has any reasonable suspicion regarding an order or transaction, including any cancellation or modification thereof, and other aspects of the functioning of the distributed ledger technology such as the consensus mechanism, where there might exist circumstances indicating that market abuse has been committed, is being committed or is likely to be committed.
14.5 Reporting to Bitvavo
Each Participant must promptly report any suspicious activity to Bitvavo that undermines the integrity and fairness of crypto markets, that could be identified as market abuse as referred to in Title VI MiCA and/or that can be identified as one of the activities listed in this section.
14.6 Notification to Authorities
Bitvavo is authorized to notify the relevant authorities and will provide data to the relevant authorities to the extent required by law and regulation.
14.7 Reporting of Unusual Transactions
Bitvavo will report any unusual transactions to the relevant authority in line with the applicable anti-money laundering and anti-terrorism financing legislation.
15.1 Cancellation of Orders
Bitvavo may modify or cancel open Orders for any reason, including but not limited to, the following circumstances, the occurrence of which is to be determined by Bitvavo in its sole discretion:
(i) in case of Orders placed by Participants who, in Bitvavo's sole discretion, may have engaged or may have attempted to engage in abusive use of the Bitvavo Trading Platform in relation to that Order or otherwise. This may include market abuse activities or other prohibited activities as referred to in Section 14 of these Trading Rules, but may also include operational or otherwise abusive or adverse activities, such as using the API in a manner which unreasonably burdens the Bitvavo Trading Platform;
(ii) in case of Orders which involve an error with respect to price, quantity, or other parameters;
(iii) if required by any applicable law or regulation;
(iv) upon instruction of competent authorities or court order; or
(v) if required for technical reasons.
15.2 Suspension of Account
Bitvavo may suspend or block specific or all use of an Account, suspend or cancel any pending Order or PG request (including any requests to modify or cancel an Order), any transaction, suspend or cancel any deposit or withdrawal, freeze the Funds or Digital Assets related to an Account or suspend the cancellation of an Account in connection with an investigation into misuse of an Account or any Service provided by Bitvavo. If the legitimacy of any Participant or any Order, PG request or use of the Services cannot be established, such Participant may lose all rights to the Funds and Digital Assets in its Account.
15.3 Delisting
Bitvavo may at any time and in its sole discretion decide to delist Digital Assets from the Bitvavo Trading Platform. Bitvavo can do so in any circumstances, including, but not limited to:
(a) a breach of these Trading Rules by the Issuer or non-conformity of the relevant Digital Asset with these Trading Rules;
(b) any events or developments regarding the Issuer or the Digital Asset that could pose material risk to the Participants or orderly trading on the Bitvavo Trading Platform;
(c) upon the request of a supervisory authority;
(d) in case of bankruptcy of the Issuer;
(e) if the Digital Asset is outside of the risk appetite of Bitvavo;
(f) upon the substantiated request of the Issuer of the Digital Asset;
(g) in case of material changes to the Issuer or the Digital Asset;
(h) the Digital Asset fails to meet pre-set minimum liquidity thresholds; or
(i) the Digital Asset does not comply with Section 3.5 of these Trading Rules.
15.4 Consequences of Delisting
Upon delisting of a Digital Asset, trading in the Digital Assets concerned will be discontinued. Bitvavo will, where possible, timely inform of any (planned) delisting arrangements and be given the opportunity to divest or trade-away Digital Assets that are subject to delisting.
16.1 Instructions from supervisory authorities
Bitvavo shall comply with instructions from supervisory authorities, including EBA and the AFM, which may result in suspension or delisting of Digital Assets.
16.2 Access to Information
Bitvavo shall comply with requests from supervisory authorities to provide relevant data relating to Orders in Digital Assets that are advertised through its systems, or to provide access to the Order Book, or to records of transactions executed on the Bitvavo Trading Platform. Relevant data may include details of any Order or transaction, as the case may be, including personal data and other datapoints that link Orders with transactions executed on the Bitvavo Trading Platform.
17.1 Fees for admitting to trading on Bitvavo Trading Platform
Bitvavo may charge fees for the admission to trading on the Bitvavo Trading Platform as well as periodic fees in order to remain listed and available for trading on the Bitvavo Trading Platform.
17.2 Fees for trading on the Bitvavo Trading Platform
(a) Participant shall be due fees to Bitvavo for trading on the Bitvavo Trading Platform.
(b) Any fees and the relevant fee amounts shall be published by Bitvavo on the designated fee information pages on the Website and/or the Bitvavo Environment (the Fee schedule), as amended from time to time, or shall be made available to Participant otherwise. Bitvavo may make changes hereto in its sole discretion from time to time. Any changes made available to Participants shall become effective directly.
17.3 Trading Fee Structure
(a) Trading fees on the Bitvavo Trading Platform are based on each Participant's trading volume from the previous 30 days in accordance with the Fee Schedule as published on the Bitvavo website from time to time.
(b) The total fee amount that is charged for a trade depends on the following:
(i) the total cost (value) of the Order;
(ii) the currency pair that is being traded;
(iii) the 30-day trading volume of the participant; and
(iv) whether an Order is maker or taker.
17.4 Calculation of the Fees
(a) The fee is charged (and rebates are given) in the quote asset.
(b) Fees are calculated for each fill.
(c) Fees are rounded up, to the precision of the asset.
(d) Fees are averaged for each Order. This means that if one fill has paid more in fees than required, the next fill pays a lower fee, so that the average fee paid equals or exceeds the fee tier the Participant is in. This process may be conducted manually after the settlement has been done.
(e) The 30-day rolling volume used to determine the fee tier is calculated in EUR, at 00:00 UTC each day.
(f) All Participants pay the fees mentioned in the Fees Schedule.
(g) Bitvavo may temporarily increase or decrease the fee tier for Market Makers and large institutions (determined on a case-by-case basis).
17.5 Payment of Fees
Bitvavo may charge any fees and costs to the Participant, including but not limited to trading fees, by deducting these from Participantās Funds, Digital Assets or Bitvavo E-Token Wallet.
Bitvavo reserves the right to amend, add, or remove parts of the Trading Rules at any time and in its sole discretion. Participant will be notified of any changes and although Bitvavo will endeavour to provide Participant with advance notice, Bitvavo may indicate that the revised Trading Rules shall be effective immediately. If Participant does not agree with any such modification, Participant must close its Bitvavo Account and cease using the Bitvavo Trading Platform. If Participant continues to use the Bitvavo Trading Platform after a modification, Participant is deemed to have accepted and agreed to the amendments. It is the Participant's responsibility to review the amended Trading Rules.
07 May 2026
1 Definitions
1.1 Account has the meaning given thereto in the User Agreement. The term Account also refers to the Master Account and and the Sub-Accounts associated with the Master Account where applicable.
1.2 AFM means the Dutch Authority for Financial Markets (Autoriteit Financiƫle Markten).
1.3 Algorithmic Trading means the use of computer algorithms that automatically determine individual parameters of orders resulting in investment and/or execution decisions based on predefined criteria and strategies with limited or no human intervention.
1.4 Affiliate has the meaning given thereto in the User Agreement.
1.5 API means Application Programming Interface.
1.6 API Credentials means the API key(s) with corresponding secrets.
1.7 API Trading Bot means an automated software application that interacts with the Bitvavo Trading Platform via API to execute trades based on predefined algorithms or strategies.
1.8 App has the meaning given thereto in the User Agreement.
1.9 Auction means the process as described in Section 6.8 of these Trading Rules.
1.10 Broker means a Participant as referred to in Section 4.6 of these Trading Rules.
1.11 Bitvavo means Bitvavo B.V.
1.12 Bitvavo Custody means Bitvavo Custody B.V.
1.13 Bitvavo E-Token has the meaning given thereto in the User Agreement.
1.14 Bitvavo Trading Platform means the Digital Asset trading platform operated by Bitvavo, including CLOB and RfQ Segment and any other trading system established and operated by Bitvavo.
1.15 Cancel Only means the status of the Bitvavo Trading Platform whereby Participants are restricted to cancelling existing orders, either for a specific Digital Asset or on the entire trading platform.
1.16 CASP means a crypto-asset service provider as defined in MiCA.
1.17 CLOB means central limit order book.
1.18 Convert means a transaction whereby a Participant buys or sells a Digital Asset against another Digital Asset.
1.19 Convert Order means an Order for buying or selling a Digital Asset Against another Digital Asset.
1.20 Corporate Participant is a Participant as referred to Section 4.4 of these Trading Rules.
1.21 Digital Asset has the meaning given thereto in the User Agreement.
1.22 EBA means European Banking Authority.
1.23 EEA means European Economic Area.
1.24 Fee means any charge or cost imposed by Bitvavo or an Affiliate, as applicable) on an Issuer or a Participant for the execution of transactions, provision of Services, or maintenance of an Account, admission to trading or otherwise.
1.25 Funds has the meaning given thereto in the User Agreement.
1.26 Halted means the status of the Bitvavo Trading Platform whereby there is a temporary suspension of trading activity, either for a specific Digital Asset or on the entire trading platform.
1.27 High Frequency Trading means an infrastructure intended to minimise network and other types of latencies that enable Algorithmic Trading at high speed.
1.28 Issuer means issuer as defined in MiCA.
1.29 Limit Order means an Order as described in Section 6.1(a)(ii) of these Trading Rules.
1.30 Market Maker means a Participant as referred to in Section 4.5 of these Trading Rules.
1.31 Market Order means an Order as described in Section 6.1(a)(i) of these Trading Rules.
1.32 Market Specification means the document that describes the attributes of a specific Digital Asset as defined in Section 5.7 of these Trading Rules.
1.33 Master Account means the Account of a Participant (other than Retail Participant), that could be composed of one or more Sub-Accounts.
1.34 MiCA means Regulation (EU) 2023/1114 on markets in crypto-assets, as amended or supplemented from time to time.
1.35 Order means an instruction to buy or sell Digital Assets on the Bitvavo Trading Platform.
1.36 Order Book means a digital ledger maintained by Bitvavo that records all buy and sell orders for a specific cryptocurrency pair.
1.37 Participant means any natural person or legal entity that engages in trading activities on the Bitvavo Trading Platform.
1.38 Price Guarantee Service means the price guarantee service, which is a service provided by Bitvavo that protects the Participant against price fluctuations in a specific Digital Asset for a pre-defined period of time.
1.39 Reference Price has the meaning given thereto in Section 6.3 (f) of these Trading Rules.
1.40 RfQ means Request for Quote.
1.41 RfQ Segment means the segment of the Bitvavo Trading Platform where Orders of the Participants are routed pursuant to these Trading Rules.
1.42 Retail Participant is a Participant as referred to in Section 4.3 of these Trading Rules.
1.43 Services has the meaning given thereto in the User Agreement.
1.44 Stop Loss Order means an Order as described in Section 6.1(b)(i) of these Trading Rules.
1.45 Stop Loss Limit Order means an Order as described in Section 6.1(b)(ii) of these Trading Rules.
1.46 Sub-Account means an administrative sub-account held by a Participant (other than a Retail Participant) which is connected to a Master Account that is held by the Participant.
1.47 Take Profit Order means an Order as described in Section 6.1(b)(iii) of these Trading Rules.
1.48 Take Profit Limit Order means an Order as described in Section 6.1(b)(iv) of these Trading Rules.
1.49 Tick Size means the minimum price increment between two valid order prices for a market. Orders must be priced in multiples of the configured tick size.
1.50 Trading Bots means any automated software, script, algorithm, or service - proprietary or third-party - that accesses the Bitvavo Trading Platform via APIs to submit, modify, or cancel Orders, or to make trading decisions without a human initiating each action.
1.51 Trading Rules means these trading rules.
1.52 US Person means a United States citizen or resident individual, a partnership or corporation organized in the United States or under the laws of the United States or any State thereof, a trust if (i) a court within the United States would have authority under applicable law to render orders or judgments concerning substantially all issues regarding administration of the trust, and (ii) one or more U.S. persons have the authority to control all substantial decisions of the trust, or an estate of a decedent that is a citizen or resident of the United States, a branch or an agency of a foreign entity which is located in the U.S, or any non-discretionary or similar account (other than an estate or trust) held by a dealer or other fiduciary for the account or benefit of a U.S person, or any discretionary account or similar account (other than an estate or trust) held by a dealer or other fiduciary organized, incorporated, or (if an individual) resident in the United States
1.53 User Agreement means the contractual agreement between the Participant, Bitvavo, Bitvavo Custody B.V. which defines and governs the provision of the Services by the relevant entities and the use of the Services by Participants.
1.54 Website has the meaning given thereto in the User Agreement.
Any capitalized term not defined in these Trading Rules shall have the meanings given to them in the User Agreement.
2 General information
2.1 The Bitvavo Trading Platform
Bitvavo operates a trading platform which manages several trading systems such as the CLOB segment and the RfQ segment, where Digital Assets can be purchased or sold, resulting in the exchange of Funds for Digital Assets and Digital Assets for other Digital Assets (āthe Bitvavo Trading Platformā).
These Trading Rules govern terms applicable to the trading on Bitvavo Trading Platform, ensure compliance with Article 76 MiCA and promote fair, efficient and transparent trading on the Bitvavo Trading Platform.
2.2 Licence
Bitvavo is licensed by the AFM under the registration number 41000010, as a CASP under MiCA and is permitted to provide the Digital Asset service of operation of a trading platform for crypto assets, custody and administration of crypto assets and transfer services for crypto assets. These Services are available in all EEA jurisdictions.
Bitvavo reserves the right to not make the Bitvavo Trading Platform available in all markets or jurisdictions where it is authorized or permitted to provide its Services, and may restrict or prohibit the use of the Bitvavo Trading Platform by residents of certain jurisdictions.
For the avoidance of doubt, Lending Services are provided by Bitvavo Custody B.V. solely and Bitvavo Custody B.V is not subject to the supervision of the AFM.
Staking Services, Lending Services, Margin Trading Facility and Price Guarantee Services are not services regulated under MICA and involve certain risks, while using these services you may not be subject to the safeguards and protections under MICA.
3 Digital Assets ā Admission to trading
3.1 Requirements for (Issuers of) Digital Assets seeking admission to trading at Bitvavo
(a) Bitvavo has implemented a Digital Asset admission processĀ based on which Bitvavo determines whether a new Digital Asset can be admitted to trading on the Bitvavo Trading Platform. Bitvavo may in its sole discretion determine whether or not a Digital Asset can be admitted to trading on the Bitvavo Trading Platform.
(b) Each Digital Asset to be admitted to trading on the Bitvavo Trading Platform should meet and continue to meet requirements on its business case, feasibility, compliance, legal, risk and suitability requirements as set by Bitvavo from time to time.
3.2 Application procedure for admission to trading at Bitvavo
The application procedure will be carried out in accordance with Bitvavoās policies and procedures. In summary, Bitvavo considers the following criteria:
(a) a business case assessment (including market viability and economic and strategic fundamentals) and pre-scan (for the feasibility and compliance assessment);
(b) a feasibility assessment (including custody, liquidity and blockchain integration);
(c) a compliance, legal and risk assessment (compliance with applicable laws, KYC, customer due diligence assessments proportionate to the risk profile of the applicant, audit and privacy and the risks associated with the Digital Asset);
(d) a suitability assessment (asset value, security, technology and additional risk and compliance requirements); and
(e) admission to go-live preparation (date, technological preparation, liquidity, inventory, and communication).
3.3 Conditions for Digital Assets to remain admitted to trading
(a) Liquidity thresholds
To remain eligible for trading, each Digital Asset that is admitted to trading on the Bitvavo Trading Platform must consistently achieve a daily average transaction volume that meets or exceeds the threshold periodically set by Bitvavo.
(b) Disclosure requirements
To remain eligible for trading, Issuers of Digital Assets must at minimum disclose the following information on their website:
(i) a Digital Asset whitepaper in compliance with the requirements in MiCA, if applicable; and
(ii) whenever there is a significant new factor, material mistake or material inaccuracy that can affect the assessment of the Digital Assets, the modified Digital Asset whitepaper, including the reasons for such modification, in accordance with MiCA, if applicable.
3.4 Ongoing monitoring of Issuers and Digital Assets
(a) To ensure continued credibility, security and efficiency of its markets and the Digital Assets that are admitted to trading and their compliance with this Section 3 of the Trading Rules, BitvavoĀ continuously monitors applicable risk factors that would possibly lead to a trading suspension or a delisting of any admitted Digital Assets. To perform this ongoing monitoring, Bitvavo leverages automated alerts and tooling that may prompt re-evaluations of Digital Assets admitted to trading, taking into account developments in the Digital Assets market, including regulatory changes, technological issues or changes, market dynamics, liquidity and concentration of the Digital Assets.
(b) With regard to liquidity, Bitvavo assesses whether the liquidity provided by Market Makers to the Order Book is appropriately aligned with the Order volumes in the Order Book. Bitvavo also assesses the trading activity in the relevant Digital Asset on other Digital Asset trading platforms.
3.5 Digital Assets Not Admitted to Trading at the Bitvavo Trading Platform
A Digital Asset is not admitted to trading on the Bitvavo Trading Platform if:
(a) it does not pass the application procedure as referred to in Section 3.2 of these Trading Rules;
(b) no corresponding Digital Asset white paper has been published in the cases required by MiCA; or
(c) it has an inbuilt anonymization function, unless the holders and transaction history can be identified by Bitvavo.
4 Participants
4.1 Participant criteria
A person can be a Participant of the Bitvavo Trading Platform if:
(a) the person has created an Account as set out in the User Agreement;
(b) the person has accepted the User Agreement and these Trading Rules.
(c) the person complies with mandatory regulatory obligations related to Market Abuse prevention, AML/CFT/PSE rules and regulatory licensing requirements (if applicable) at Bitvavoās sole discretion; and
(d) Bitvavo has accepted this person as a Participant.
4.2 Participant categories
Bitvavo distinguishes four categories of Participants:
(a) Retail Participants;
(b) Corporate Participants;
(c) Market Makers; and
(d) Brokers (including, but not limited to, providers of trading bots or other services through the Bitvavo API).
4.3 Retail Participants
A Retail Participant can be a natural person that is at least 18 years old, that is not a US Person and that is resident in a jurisdiction in the EEA where Bitvavo Services are available.
4.4 Corporate Participants
A Corporate Participant can be a legal entity that is not a Market Maker or a Broker and that is resident or established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its Services.
4.5 Market Makers
A Market Maker can be a natural person or legal entity that has entered into a market making agreement with Bitvavo and that complies with the terms thereof, the User Agreement and any other agreement concluded with Bitvavo or Bitvavo Custody. A market making agreement includes specific terms and conditions to obtain access to the Bitvavo Trading Platform as a Marker Maker, such as, amongst others, the Digital Assets covered by the market making agreement, minimum up-times and response times, the streaming of prices/quotes on both sides of the market, spread limits, fees, credit lines, incentives and penalties for non-compliance.
4.6 Brokers
A Broker can be a legal entity that is a resident or is established in a jurisdiction in the EEA where Bitvavo is authorized or permitted to provide its services, and, if applicable, is authorised to provide crypto-asset services as defined in MiCA, and that complies with the terms of any agreement with Bitvavo. A Broker operating one or more Trading Bots that wants to access the Bitvavo Trading Platform must agree to the Bitvavo Developer Agreement and/or the API Partner Agreement.
4.7 Trading limits
(a) Bitvavo applies trading limits to the Account of Participants, including daily, weekly, monthly, annually and total limits. Bitvavo may set such limits in its sole discretion, based on the information provided by Participant and any other information available to Bitvavo (including, but not limited to, the Account balance of the Participant, the trading behaviour of the Participant, the capacity and resilience of the Bitvavo Trading Platform and the market for each relevant Digital Asset).
(b) Bitvavo may include the different trading limit thresholds as an indication on its Website. Bitvavo can amend the procedures and limits from time to time without prior notice and with immediate effect.
(c) Bitvavo may require a Participant to provide or verify additional information, or to wait some period of time after execution of a trade or a transaction, before settlement of such trade and before permitting a Participant to enter into any subsequent trades on the Bitvavo Trading Platform.
(d) A Participant may submit a request for higher limits. Bitvavo may require the Participant to submit additional documentation in this regard and does not guarantee that limits will be raised as requested.
5 Trading - General
5.1 Trading Days and Trading Hours
The Bitvavo Trading Platform is available for trading every day, 24 hours per day, except for scheduled or unscheduled down-time or except as stated in rules specific to a market segment. Specific trading conditions may apply from time to time, for all admitted Digital Assets or on an asset-by-asset basis, for example during a specific status as determined by Bitvavo, including Halted markets, Cancel Only markets or during Auction periods, as set out in these Trading Rules.
5.2 Transactions
(a) Participants can submit instructions to buy or sell Digital Assets on the Bitvavo Trading Platform (placing an Order), against other Digital Assets or Funds where pairs are offered by Bitvavo from time to time (geographical restrictions may apply).
(b) Bitvavo is not a Participant and Bitvavo will not act as a counterparty of a Participant in any transaction in Digital Assets executed on the Bitvavo Trading Platform.
(c) The Participant is solely responsible for placing Orders and providing any other instructions.
(d) Bitvavo or other Participants may provide information on Digital Assets, including, but not limited to, the price and volatility. This information as well as any other information on the Bitvavo Trading Platform does not constitute investment advice, a recommendation to sell or buy or an opinion of Bitvavo.
(e) The price indicated on the transaction confirmation is the price at which an Order has been executed. This price may deviate from prices indicated or referenced on the Bitvavo Trading Platform prior to the execution of an Order. The price indicated on the transaction confirmation is always conclusive over other price indications.
5.3 Recurring Buy
(a) Participants can automatically buy selected Digital Assets on a monthly basis by switching on the āRecurring Buyā feature.
(b) By using this feature, Participants authorise Bitvavo to deduct Funds and Fees directly from their Account at a random timestamp on a certain day of each month as selected by the Participant.
5.4 Holding of Funds
Once an Order to buy Digital Assets is placed, a certain amount of Funds is placed on hold in the Participantās Account. This means that these Funds can only be used to fulfil the Order for which they are reserved. The amount of Funds that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Funds on hold accordingly.
5.5 Holding of Digital Assets
Once an Order to sell Digital Assets is placed, a certain amount of Digital Assets is placed on hold in the Participantās Account. This means that these Digital Assets can only be used to fulfil the Order for which they are reserved. The amount of Digital Assets that is placed on hold, varies for Limit Orders and Market Orders. Amounts placed on hold are rounded up. Cancelling an Order returns the remaining amount on hold back to the account. A fill or partial fill reduces the remaining amount of Digital Assets on hold accordingly.
5.6 Orders and Market Segments
(a) If a Participant has enabled the Price Guarantee Service, Orders that are eligible for Price Guarantee Service that are submitted by the Participant are considered an RfQ (Request for Quote) and will be routed to the RfQ Segment.
(b) All Orders in Digital Assets for sale and purchase of a Digital Asset against another Digital Asset (Convert Order) are also treated as RfQ (Request for Quote) and will be routed to the RfQ Segment. Convert feature is currently only available on the RfQ Segment and is subject to the terms applicable to the RfQ Segment including the rules on Price Guarantee Service.
(c) All other Orders will be routed to the CLOB segment.
(d) Bitvavo has the sole discretion to decide on which market segment a Digital Asset may be traded and may require certain Digital Assets to be traded on an RfQ-only basis where the liquidity of certain Digital Assets changes.
(e) Bitvavo has the sole discretion to form different market segments, define and change terms applicable to such market segments.
5.7 Market Specifications
(a) Bitvavo will publish Market Specifications detailing the terms of any Digital Assets admitted to trading on the Bitvavo Trading Platform.
(b) Bitvavo may amend, at its sole discretion, the Market Specifications and such amendments shall be communicated to Participants on reasonable notice.
5.8 Cancellation of transactions
5.8.1 Bitvavo may, in its sole discretion, or following a request by a Participant, conduct a review of a transaction executed on the Bitvavo Trading Platform where (i) there is a reasonable basis to believe that such transaction has been executed as a result of an erroneously submitted Order, or (ii) executed in violation of applicable laws and regulations (including market abuse) and these Trading Rules, (iii) or where so requested by competent authorities or courts, (iv) or for the reasons stipulated in the User Agreement.
5.8.2. Bitvavo shall notify the relevant Participants to a transaction of the result of an investigation into one or more transactions.
5.8.3. If Bitvavo, at its sole discretion, determines the transaction subject to an investigation is clearly erroneous or executed in violation of applicable laws and regulations, Bitvavo may nullify the transaction, un-wind the fund movements resulting from the transaction and may notify the affected Participant(s) accordingly. This Article 5.8.3 also covers rules on prevention of market abuse, prevention of market manipulation, prevention of abuse of market practices, prevention of improper trading, or any other breach of these Trading Rules, the User Agreement or principles of fair and orderly trading. This Article 5.8.3 also covers any execution as a result of a manifest error, technical malfunction or abuse of the Bitvavo Trading Platform. Clearly covered by Article 5.8.3 are Funds and Digital Assets constituting one leg of the settlement of a transaction connected to, derived from, or intended for use in illegal, unlawful or illegitimate activities. This includes but is not limited to fraud, money laundering, terrorist financing, market abuse, sanctions violations or other criminal offences and breaches of these Trading Rules, or supposed violations claimed by competent authorities or legal acts by courts.
5.9. Master Account and Sub Accounts
5.9.1. Participants, other than Retail Participants, may be allowed to have Sub-Accounts connected to a Master Account.
5.9.2. Bitvavo may set trading limits per Sub-Account and a cumulative trading limit for the Master Account pursuant to Section 4.7 of these Trading Rules. Participants may not exceed these trading limits.
5.9.3. Each Participant can only have one Master Account, Bitvavo may limit the number of the Sub-Accounts.
5.9.4. Participants may not use the Master Account or Sub-Accounts in violation of these Trading Rules or the User Agreement.
6 Trading ā Central Limit Order Book
6.1 Order Options
(a) The main Order options available on the Bitvavo Trading Platform are a Market Order or a Limit Order.
(i) Market Order:
(A) A Market Order is matched with the best-priced Limit Order in the Order Book at the time of the request. If there are more than one such Limit Orders, the Market Order is matched with the oldest one.
(B) There is no guarantee that a Market Order will fill at the market price indicated. A Market Order may fill at a number of different prices, based on the quantity of the Market Order and the quantities and direction of the existing Orders in the Order Book at the time.
(ii) Limit Order:
(A) A Limit Order is an Order to buy or sell at a fixed price.
(B) A Limit Order will be executed if or when the market price reaches the limit price and will be filled at the limit price or better.
(1) A buy Limit Order will be executed only at the limit price or a lower price.
(2) A sell Limit Order will be executed only at the limit price or a higher price.
(b) Additional advanced order options that may be available on the Bitvavo Trading Platform are Stop Loss Order, Stop Loss Limit Order, Take Profit Order, Take Profit Limit Order and One-Cancels-the-Other. The availability of these order options may depend on the method of access to the Bitvavo Trading Platform.
(i) Stop Loss Order:
(A) A Stop Loss Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches a specified trigger price in order to limit Participant losses.
(B) Once a Stop Loss Order has been placed, it is considered āactiveā until cancelled or until the relevant Market Order is placed, when the stop price has been triggered.
(C) A Stop Loss Order is not posted to the Order Book and is not visible to other Participants.
(ii) Stop Loss Limit Order:
(A) Stop Loss Limit Order mechanics are similar to Stop Loss Order with the main difference that Stop Loss Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
(iii) Take Profit Order:
(A) A Take Profit Order is an instruction to place a Market Order to buy or sell a Digital Asset once its price reaches the take profit price to realise Participant profits.
(B) Once a Take Profit Order has been placed, it is considered āactiveā until it is cancelled or until the relevant Market Order has been placed when the trigger price is reached.
(C) A Take Profit Order is not posted to the Order Book and is not visible to other Participants.
(iv) Take Profit Limit Order:
(A) Take Profit Limit Order mechanics are similar to Take Profit Order with the main difference that Take Profit Limit Order creates a Limit Order instead of a Market Order once a Digital Asset reaches a specified price.
(v) One-Cancels-the-Other
(A) This Order type enables Participants to place two linked conditional Orders, (i) a Take Profit or a Take Profit Limit Order and (ii) a Stop Loss or a Stop Loss Limit Order where the triggering of one leg of the Order will result in the automatic cancellation of the other Order.
(B) In this Order type, both legs of the Order should be of the same direction i.e. sell side for both legs or buy side for both legs of the Order.
6.2 Submission and execution of Orders
(a) An Order is submitted by a Participant via the App, Website or API. The Participant selects the Digital Asset it wants to buy or sell and enters the Order details. Subsequently, the Participant submits the Order to the Order Book.
(b) Once the Order is submitted by the Participant and received by the Bitvavo Trading Platform system, Bitvavo performs a validation of the Order details, including if the Participantās balance is sufficient, the market protection checks as set out in Section 6.3 of these Trading Rules and whether, in Bitvavoās sole discretion, the Order contains all the relevant datapoints as pertaining to the Order, including datapoints that are required for Bitvavo to comply with applicable regulations or any other datapoints to be included in any Order. If the Order fails any of these checks, the Order is rejected and the Participant is notified. If the Order passes these checks, the Order is accepted by Bitvavo, entered into the Order Book and the Participant is notified.
(c) Once accepted into the Order Book, the Order is either matched with another existing Order in the Order Book with an opposite direction, or is added to the Order Book. If an Order is matched with another Order, this results in the execution of the Order in line with Section 6.5 - 6.8 of these Trading Rules. The Participant receives confirmation of such execution.
(d) An Order has the following parameters:
(i) Market: Name of the market, in the format BASE-QUOTE (e.g. BTC-EUR).
(ii) Side: Buy or sell.
(iii) Order Type: Limit Order or Market Order. When placing a Limit Order, the Order might still be executed against a better price than specified, in which case it is processed as a Market Order. There is also a possibility to submit advanced order types as described in Section 6.3.
(iv) Amount: The quantity of the base asset to be bought/sold (required for Limit Orders, optional for Market Orders). Applicable quantity decimal precisions are detailed in the relevant Market Specification.
(v) Amount Quote: The amount specified in the quote asset (optional for Market Orders, either Amount or Amount Quote is required)
(vi) Price: The price for base asset specified in the quote asset (required for Limit Orders). Applicable Tick Sizes are detailed in the relevant Market Specification.
(vii) Time In Force: This specifies how long the Order should be placed on the Order Book. This only applies to Limit Orders. The following options are allowed:
(A) GTC: Good-Til-Cancelled. This is the default setting and places an order on the Order Book until it is filled or cancelled.
(B) IOC: Immediate-Or-Cancel. This allows (partial) filling of the Order when it is submitted. The remaining amount that cannot be matched immediately will be cancelled.
(C) FOK: Fill-Or-Kill. This ensures that the entire Order is either filled or cancelled. Partial fills are not possible.
(viii) Self-Trade Prevention: Trading with oneself is not allowed. This setting handles what should be done if a Participantās Order would match with one of the Participantās own orders. The following options are allowed:
(A) Decrement And Cancel: This is the default setting and modifies both Orders by the amount that would have been filled. This results in the smaller of the two Orders being cancelled, and the other Order being reduced in size.
(B) Cancel Oldest: Cancels the oldest Order.
(C) Cancel Newest: Cancels the newest order.
(D) Cancel Both: Cancels both Orders.
(ix) Post Only: Limit Orders that have this set to true will be cancelled if matched immediately. This ensures that the Participant pays the maker fee and not the taker fee. As a default, Post Only is switched off.
(x) Response Required: If this value is set to false, only the Order ID of the newly created Order is returned. The default value is true (i.e. a full response).
6.3 Market Protections
(a) Order Minimums/Maximums
All Market Orders, Limit Orders, and Stop OrdersĀ placed on the Bitvavo Trading Platform are subject to minimum and maximum Order Amount and Amount Quote requirements per market.
(b) Number of Open Orders
All Participants are subject to a maximum number of Orders that may be open in the Order Book per market. When a Participant reaches the limit in a given market, any Orders entered in that market thereafter are rejected until the number of open Orders stored in the Order Book for the given market decreases below the limit.
(c) Placement Price Protection
Limit Orders with a Good-Til-Cancelled Time in Force are subject to a Placement Price Protection. Buy (Sell) Limit Orders with a price lower (higher) than the lower (upper) Placement Price Protection Band will be rejected.
(i) The Upper Placement Price Protection Band is calculated by multiplying the Placement Price Multiplier times the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed.
(ii) The Lower Placement Price Protection Band is calculated by dividing the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed by the Placement Price Multiplier.
(d) Execution Price Protection
Limit Orders are subject to an Execution Price Protection. Buy (Sell) Limit Orders with a price higher (lower) than the upper (lower) Execution Price Protection Band will be rejected.
(i) The Upper Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed plus the Execution Protection Threshold percentage.
(ii) The Lower Execution Price Protection Band is calculated as the mid-point price between the best bid and best offer on the Order Book at the time the Limit Order is placed minus the Execution Protection Threshold percentage.
(e) Spread Price Protection
(i) Market Orders are subject to a Spread Price Protection. Market Orders will fill at prices up to the Spread Protection Threshold from the mid-point price between the best bid and best offer on the Order Book at the time the Market Order is placed. If a Market Order would fill against Orders beyond the Spread Protection Threshold, the Order will partially fill up to the Spread Protection Threshold level and all the remaining quantity of the Order will be cancelled.
(f) Reference Price Protection
All Orders are subject to Reference Price Protection, which limits how far the price at which an Order is executed, can deviate from the market price at the time the Order is placed (the āReference Priceā).
The Reference Price is an index price, calculated using price data from multiple external exchanges to reflect a fair market value for the Digital Asset. Orders will only be filled at prices within what is known as the āReference Price Protection Thresholdā, which is a defined range from this Reference Price. If the price at which an Order would be filled falls outside this threshold, only the portion of the Order within the threshold will be filled; the rest will be cancelled. This may result in some Orders being partially filled.
If a valid reference price is unavailable, or if Bitvavo determines that the index does not accurately represent current market conditions, this protection will not apply.
(g) Cancel on Disconnect
Cancel on Disconnect is a risk management feature that automatically triggers a cancellation of all open Orders placed by a Participant if there is a loss of connection to the Trading Platform for a period specified by the Participant.
Participants can group certain Digital Assets whereby each group would be subject to a different inactivity period after which open Orders in all Digital Assets in such group will be automatically cancelled.
This feature is available to Participants who opt-in for this feature. Bitvavo reserves the right to make this function available to only advanced Participants. Cancellation of open Orders will be processed within the general rules applicable to cancellation, Bitvavo does not guarantee automatic or immediate cancellation.
(h) General note for this section
The limits, multipliers and thresholds used for this section 6.3 shall be determined by Bitvavo for each market.
6.4 Errors
(a) In exceptional cases, there may be errors in the Bitvavo Trading Platform, including in relation to the prices displayed or the way in which Orders are matched. In addition, the Digital Assets on the Bitvavo Trading Platform may be subject to unusual price movements, including as a result of market manipulation or sudden drops or spikes in liquidity. In such cases, Bitvavo may at its sole discretion (and is in no way obliged to):
(i) retrospectively correct any such errors or rectify any such price movements, including by amending or reverting transactions, which may be to the advantage or to the disadvantage of Participant; or
(ii) temporarily or indefinitely halt trading on the Bitvavo Trading Platform for one or more Digital Assets;
(b) Especially during periods of high volume, illiquidity, fast movement or volatility, any Digital Assets traded on the Bitvavo Trading Platform may be executed at a different rate than displayed to the Participant at the time of Participants Order.
(c) Ā In the case of suspected fraud or misuse, Bitvavo reserves the right to suspend or cancel Orders and transactions until the legitimacy has been verified.
6.5 Order Matching and Execution During Regular Trading
(a) Orders that are matched immediately are taker orders. Orders that are not matched immediately and are placed in the Order Book are maker orders.
(b) Limit Orders may be maker or taker orders, depending on whether the Limit Order can be matched immediately. If matched immediately, the Limit order is a taker order. If placed on the Order Book, the Limit Order is a maker order.
(c) Orders are matched based on price-time priority. This means that taker Orders are matched with the maker Orders with the best available price. If several Orders have the same price, the oldest maker Order is matched. This process continues until the Order is filled, placed on the Order Book, or cancelled.
(d) The price paid/received is determined by the maker order. This means that Limit Orders can be filled at prices better than their limit price.
(e) Fills may be settled nearly instantly or after a period of time.
(f) The execution price of a Market Order may differ significantly from the indicated price. This may be due to a change in price between the time of the Order being initiated by the Participant and the execution of the Order (i.e. 'slippage').
(g) Market Orders, Limit Orders, and stop Limit Orders are not guaranteed executable due to the required availability of sufficient supply or demand.
(h) Orders may be executed instantly or after a period of time and will be considered to have taken place at the execution date and time.
6.6 Order Matching During Halted Markets
(a) Bitvavo may, in its discretion, temporarily halt trading in a market to preserve market integrity, orderly trading conditions, and/or to conduct regular scheduled maintenance.
(b) Orders cannot be placed, modified or cancelled when a market is Halted.
(c) No order matching occurs when a market is Halted.
(d) No Order Book updates will be broadcasted when a market is Halted.
6.7 Order Matching During Cancel Only Markets
(a) Bitvavo may, in its sole discretion, temporarily set Cancel Only in a market to preserve market integrity and/or to conduct regular scheduled maintenance.
(b) Orders can be cancelled when a market is in Cancel Only status.
(c) Orders cannot be placed or modified when a market is in Cancel Only status.
(d) No order matching occurs when a market is in Cancel Only status.
6.8 Order Matching During Auctions
(a) Bitvavo employs an Auction methodology after a market has been Halted or put into Cancel Only before Regular Trading resumes to guarantee price discovery and orderly markets.
(b) The Auction process consists of two phases:
(i) Auction Collection:
(A) A Participant cannot place a Market Order when a market is at the Auction Collection phase.
(B) A Participant can place, modify or cancel all other Order types when a market is at an Auction Collection phase.
(C) No Orders will be matched during the Auction Collection.
(ii) Auction Matching:
(A) A Participant cannot place, modify or cancel Orders when a market is at the Auction Matching phase.
(B) During this period, Orders will be matched in accordance with the procedure as set out below.
(C) Active Limit Orders are used to determine the price at which the most units of the base asset are traded. If there is no price where trades occur, no matching occurs and Regular Trading resumes.
(D) If a price is obtained in the previous step, this price is used to prevent self-trades (according to the specifications made by the User regarding the treatment of its Orders for self trade prevention).
(E) Orders are matched based on price-time priority and all Orders are considered taker orders. Limit Orders with the best price will be filled first, at the price determined in step (1).
(F) When no more Limit Orders can be matched at the determined price, Buy Post-Only Orders with a price above the determined price and Sell Post-Only Orders with a price below the determined price are cancelled and Regular Trading resumes.
(c) No Order Book updates will be broadcasted when a market is at Auction phase.
7 Trading
7.1 Price Guarantee Service
The Price Guarantee Service protects the Participant against price fluctuations in a specific Digital Asset for a period of 5 seconds upon submission of the Order. This market risk is absorbed by the Participant interacting on the RfQ Segment and responding to RfQ. To account for the market risk taken by the Participant between the time of the Participantās quote and the execution of the Order, each quote may include a compensation (spread).
7.2 Price Guarantee Trades
(a) An Order via the Price Guarantee Service will result in a trade when the Participant has accepted the quote that has been shown to it in response to the opening of the order form and the entering of the relevant details of the order by the Participant.
(b) If a quote under the RfQ Segment is accepted in a timely manner by a Participant, the RfQ will be executed under the Price Guarantee Service terms set out herein, and such RfQ will be deemed a taker order of that Participant.
7.3 Price Guarantee Quoting Process
If a quote is not accepted by a Participant within five (5) seconds, the quote will be refreshed with a new quote, which will again be valid for five (5) seconds. This process is repeated until a Participant accepts a quote, which will result in a (partial or entire) execution of the PG Order. Alternatively, the process ends when a Participant does not accept a quote and exits the order form for a specific crypto pair. If there are no available quotes on the RfQ Segment then the Participant will be prompted to execute a standard Market Order.
7.4 Quotes on the RfQ Segment
Prices of the quotes provided by Participants interacting on the RfQ Segment in response to RfQ must remain within a predetermined range. Only quotes that fall within this range will be considered by Bitvavoās matching engine in selecting the best quote (best from the Participant's perspective) that will be displayed to the Participant in response to a given RfQ.
7.5 Algorithmic Trading
Participants may engage in Algorithmic Trading on the Bitvavo Trading Platform provided that:
(a) the Participant has given prior notice to Bitvavo each time it wishes to deploy a new algorithm or a material change to an algorithm on the Bitvavo Trading Platform and provide a description of the algorithm including a unique identification number assigned to such algorithm, which shall be included in any order or quote generated or governed by such algorithm. Participant shall update such details and identification number upon each material change of the algorithm;
(b) prior to deployment of any algorithm on the Bitvavo Trading Platform, the Participant has performed appropriate and successful testing of each algorithm ensuring an algorithm does not contribute to or create disorderly market conditions on the Bitvavo Trading Platform;
(c) upon Bitvavoās instruction, the Participant shall use the testing environment made available by Bitvavo for purposes of conformance testing any new algorithm or substantial change to an algorithm, prior to deployment on the Bitvavo Trading Platform;
(d) each algorithm on the Bitvavo Trading Platform shall comply with Bitvavoās Trading Rules and applicable regulations;
(e) upon Bitvavoās request, the Participant shall provide certification in writing of the successful testing for each algorithm to be deployed on the Bitvavo Trading Platform, including for each substantial change thereto prior to the deployment on the Bitvavo Trading Platform;
(f) each of their algorithms deployed on the Bitvavo Trading Platform is continuously monitored by the Participant to prevent disorderly trading.
(g) the participant complies with all applicable regulatory obligations, including those relating to the prevention of market abuse, money laundering, terrorism financing, sanctions, and any relevant licensing or authorisation requirements.
7.6 Conditions to High Frequency Trading
Bitvavo may, in its sole discretion, apply conditions to the deployment of High Frequency Trading techniques on the Bitvavo Trading Platform.
7.7. Margin Trading
7.7.1 Margin Trading is a trading strategy that allows a Participant to borrow Digital Assets including Electronic Money Tokens as described in the User Agreement (āMargin Tradingā). A Participant may open a short or long position by borrowing a Digital Asset.
7.7.2 Bitvavo may allow Participants to engage in Margin Trading on Bitvavo Platform. .
7.7.3 The Participant could trade on margin by using the Margin Account. The Participant shall monitor each Margin Position, the Borrowed Assets and corresponding Margin Collateral in its Margin Account.
7.7.4 The Participant shall monitor the Health Ratio at all times to avoid Liquidation of the relevant Margin Position. If the Liquidation is triggered, Margin Collateral will be used pursuant to the terms of the User Agreement.
8 Suspension of Trading
8.1 Grounds for Suspension
Bitvavo may, in its sole discretion, suspend or remove one or more Digital Assets or Participants from trading or to suspend trading on the Bitvavo Platform in its entirety or for an individual Participant. Among others, Bitvavo can do so in the following circumstances:
(a) to prevent disorderly market conditions;
(b) upon the substantiated request of an Issuer;
(c) in case of (suspected) fraud, deception or market abuse;
(d) failure of an Issuer or a Participant to comply with these Trading Rules;
(e) failure of an Issuer or a Participant to comply with applicable legislation;
(f) in case of bankruptcy of an Issuer or a Participant;
(g) failure of an Issuer or a Participant to provide requested information to Bitvavo, or a supervisory authority;
(h) in case of technical or operational disruption;
(i) in case of the occurrence of events in the financial markets or the Digital Asset markets that may have material adverse effect on the orderly trading, integrity or resilience of the Bitvavo Trading Platform; or
(j) if deemed appropriate by Bitvavo in its sole discretion in order to protect the integrity or resilience of the Bitvavo Trading Platform, or to protect the interests of any Participant, Bitvavo or any Affiliate of Bitvavo.
8.2 Request from Supervisory Authority
Bitvavo will comply with a request of a supervisory authority to suspend or prohibit trading as referred to in Section 16 of these Trading Rules.
8.3 Suspension of Trading for Maintenance
Bitvavo may temporarily suspend trading for maintenance or for other reasons. Generally, Bitvavo will proceed according to the following steps:
(a) Announcement scheduled downtime: Participants will be informed through a message on account.bitvavo.com.
(b) Scheduled downtime begins: Participants will be informed through a message on account.bitvavo.com.
(c) Scheduled downtime ends: Markets will be placed in Halted mode. Participants will be informed through a message on account.bitvavo.com when trading resumes. This will be at least 15 minutes after the scheduled downtime ends.
8.4 Market Status During and After Suspension
During a suspension, the Bitvavo Trading Platform will be placed in Halted mode. When trading resumes after a suspension, Bitvavo will apply the Auction methodology as referred to in Section 6.8 of these Trading Rules.
9 Settlement
9.1 Settlement of Digital Assets
Bitvavo is responsible for the correct execution and settlement of the purchase and sale of Digital Assets on the Bitvavo Trading Platform in accordance with applicable regulations.
9.2 Off-Chain Settlement
All transactions on the Bitvavo Trading Platform are settled off-chain. Final settlement is generally initiated immediately or shortly after execution of a transaction on the Bitvavo Trading Platform and by the end of the Trading Day at the latest. The settlement process results in the transfer of rights associated with the traded Digital Assets from one Participant to another against the payment of the transaction price, while the Digital Assets themselves continue to be held by the Foundation, but on behalf of the acquiring Participant.
10 Transparency
10.1 Pre-Trade Transparency
Bitvavo publishes the bid and ask prices and the depth of trading interest at those prices which are advertised on the Bitvavo Trading Platform for Digital Assets in accordance with applicable regulations. Bitvavo makes this information available on a continuous basis on its website.
10.2 Post-Trade Transparency
Bitvavo publishes the price, volume and time of the transactions executed in respect of Digital Assets traded on the Bitvavo Trading Platform in accordance with applicable regulations. Bitvavo publishes this information as close to real-time as technically possible in the App and on the Website.
10.3 Access to this Information
Bitvavo makes available the information in this section on a non-discriminatory basis. The regulatory information will be made available free of charge 15 minutes after publication in a machine-readable format, and it will remain published for at least two years.
11 Availability of the Bitvavo Trading Platform
11.1 Modification and Termination of Trading
Bitvavo may, in its sole discretion, for any reason and without liability to Participant, (i)Ā modify, discontinue or terminate, temporarily or permanently, part or all of its trading services in general, and (ii) suspend, restrict or terminate Participantās access to the Bitvavo Trading Platform.
11.2 Bitvavo Trading Platform Availability
All Services are provided on an āas isā and āas availableā basis without warranty of any kind. Bitvavo does not guarantee that the Bitvavo Trading Platform will be available for any absolute or relative amount of time. Bitvavo does not warrant that access will not be interrupted or that there will be no delays, failures, errors, loss or similar of transmitted information. This may include, but is not limited to, unavailability of any of the Services during times of high volume, illiquidity, fast movement or volatility.
11.3 No Obligation to Provide Services
Bitvavo has no obligation to make available the Bitvavo Trading Platform to anyone when Bitvavo may reasonably believe that this would violate applicable laws and regulations.
12 API
12.1 Access to Bitvavo Trading Platform via API
Bitvavo may provide access to Participants to the Bitvavo Trading Platform and specific data and information through an āApplication Programming Interfaceā (API) which may be subject to additional terms and conditions as set by Bitvavo from time to time.
12.2 Use of API
To use the API, one or more API key(s) with corresponding secrets (API Credentials) must be created. The Participant is solely responsible for safeguarding the API Credentials and for any activities by the Participant or third parties that have access to the Account, whether authorized or not. In the event that the Participant knows, or should know, that API Credentials have been stolen or misused, the Participant shall contact Bitvavo immediately.
12.3 Changes to API
Bitvavo may, in its sole discretion, add, discontinue or remove, in whole or in part, the API at any time and without notice. Bitvavo cannot guarantee that future versions of the API will be backwards compatible. Participant acknowledges and understands that any of these changes may adversely affect Participantās use of the API and might require the Participant to make substantial changes in order to continue using the API, and that this is the Participantās own responsibility.
12.4 API Scope and Modifications
The scope and concrete form of the API is at Bitvavoās sole discretion. The API may be modified or abandoned at Bitvavoās sole discretion.
12.5 Monitoring of API use
Bitvavo may monitor the use of the API. The Participant will not block or otherwise interfere with the monitoring process.
12.6 API Limits
Bitvavo may set limits on the number of messages or Orders that the Participant can transmit through the API or extend limits for other Participants, in its sole discretion, during any given period and without notice. The Participant shall not attempt to circumvent such limitations. If the Participant exceeds the limits, Bitvavo may moderate the Participant activities, may cease offering access to the API or may immediately suspend or terminate access to the API in its sole discretion and without notice.
12.7 Prohibited Use of the API
The Participant shall not, and shall not encourage or authorize others to:
(a) use the API in any manner that is not expressly authorized by the User Agreement and the Trading Rules;
(b) alter, reproduce, adapt, distribute, display, publish, reverse engineer, translate, disassemble, decompile or otherwise attempt to create any source code that is derived from the API;
(c) use or access the API for purposes of monitoring the availability, performance, or functionality of any of the Services or for any other benchmarking or competitive purposes;
(d) collect, cache, aggregate, or store data or content accessed via the API other than for purposes allowed under the User Agreement;
(e) use the API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise impacts the stability of Bitvavoās servers or impacts the behaviour of other applications using the API;
(f) attempt to cloak or conceal Participantās identity when requesting authorization to the API;
(g) use the API to (i) access or use any information not permitted by the User Agreement and these Trading Rules, to (ii) circumvent or break any of Bitvavoās administrative, technical or organizational security measures, (iii) disrupt, impair, overburden or degrade the API or the Services, (iv) change the API or the Services in any way, or (v) test the vulnerabilities of the Services or API; and
(h) use any data collected from Participantās use of API for advertising purposes.
13 Access to web interfaces, API and market data
13.1 Access to Market Data
All Participants have full and equal real-time access to market data. Market data is made available through the web interfaces and Bitvavo API.
13.2 Equal Opportunity
All Participants have equal opportunity with regard to access the web interfaces and Bitvavo API.
14 Market Integrity
14.1 Market Abuse
Participants are prohibited from engaging in market abuse, including insider dealing and market manipulation as referred to in Title VI MiCA.
14.2 Market Abuse - Prohibited Activities
Without prejudice to the prohibitions as set out in Title VI MiCA, Participants are prohibited from any behaviour that may constitute market abuse, including but not limited to carrying out the following activities on the Bitvavo Trading Platform:
(a) Pump and dumps: artificially inflating the price of a Digital Asset through false and misleading positive statements, in order to sell the cheaply purchased Digital Asset at a higher price.
(b) Wash trading: Simultaneously buying and selling the same Digital Assets to create false trading volume and artificially inflate market activity.
(c) Front-running: Trading in advance of a large client order to take advantage of anticipated price movements resulting from the execution of that order. Front running involves using non-public information about future or pending transactions for their own benefit.
(d) Churning: excessive trading activity by (Broker) Participants on behalf of their clients, on either side of the Order Book, intended to increase the Participantās (Broker) commissions.
(e) Quote stuffing: quickly entering and then withdrawing large orders in an attempt to flood the market with quotes, causing competitors to lose time in processing them or causing other disorderly trading conditions.
(f) Spoofing / layering: creating the illusion of pessimism (or optimism) in the market by placing buy or sell orders without the intention of filling them.
(g) Insider trading: trading in Digital Assets based on non-public information that could affect the price of those Digital Assets.
(h) Information-based market abuse: spreading false or misleading information about crypto companies, crypto projects, Digital Assets, or market conditions to influence prices or trading activity. This includes disseminating rumours, false news, or deceptive market commentary to manipulate market participants perceptions.
(i) Improper disclosure practices: failing to disclose non-public information that could affect market prices or engaging in selective disclosure of information to certain market participants. Misleading disclosures or inadequate transparency about financial performance, risks, or other material matters related to a Digital Asset can also constitute market abuse.
14.3 Prohibition to Use the Account and the Services for Criminal Activities
A Participant may not use the Account and the Services to perform criminal activities of any sort, including but not limited to money laundering, terrorist financing, sanction evasion, fraud or any other criminal or illegal activity, the existence whereof is to be determined by Bitvavo at its sole discretion. These include, but are not limited to, the following:
(a) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to sanctions programs administered in the countries where Bitvavo conducts business, including but not limited to the EU Sanctions list.
(b) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to terrorist financing as applicable in the countries where Bitvavo conducts business.
(c) Activity which would violate, or assist in violation of, any directive, law, guideline or other regulation related to money laundering as applicable in the countries where Bitvavo conducts business.
(d) Activity which would be related to fraud such as activities which operate to defraud Bitvavo (including Participants providing any false, inaccurate, or misleading information to Bitvavo), Participants and/or other persons.
(e) Activity which would be related to drugs such as sale of narcotics, controlled substances, and any equipment designed for making or using drugs.
(f) Activity which would be related to multi-level marketing such as pyramid schemes and network marketing.
(g) Activity which would be related to unfair, predatory or deceptive practices such as investment opportunities or other services that promise (too) high rewards and sites that Bitvavo determines in its sole discretion to be unfair, deceptive, or predatory towards Participants.
(h) Activity which would be related to illegal gambling such as unregulated lotteries, sports forecasting or odds making and comparable activities.
(i) Activity which would be related to high-risk businesses such as any businesses that Bitvavo believes to pose elevated financial risk, legal liability, or violates bank policies.
(j) Activity which would be related to (attempts to) to reverse engineer, modify, translate or disassemble the (software behind the) Bitvavo Environment in whole or in part.
14.4 Reporting to the AFM
Bitvavo will report to the AFM if it has any reasonable suspicion regarding an order or transaction, including any cancellation or modification thereof, and other aspects of the functioning of the distributed ledger technology such as the consensus mechanism, where there might exist circumstances indicating that market abuse has been committed, is being committed or is likely to be committed.
14.5 Reporting to Bitvavo
Each Participant must promptly report any suspicious activity to Bitvavo that undermines the integrity and fairness of crypto markets, that could be identified as market abuse as referred to in Title VI MiCA and/or that can be identified as one of the activities listed in this section.
14.6 Notification to Authorities
Bitvavo is authorized to notify the relevant authorities and will provide data to the relevant authorities to the extent required by law and regulation.
14.7 Reporting of Unusual Transactions
Bitvavo will report any unusual transactions to the relevant authority in line with the applicable anti-money laundering and anti-terrorism financing legislation.
15 Disciplinary Actions
15.1 Cancellation of Orders
Bitvavo may modify or cancel open Orders for any reason, including but not limited to, the following circumstances, the occurrence of which is to be determined by Bitvavo in its sole discretion:
(i) in case of Orders placed by Participants who, in Bitvavo's sole discretion, may have engaged or may have attempted to engage in abusive use of the Bitvavo Trading Platform in relation to that Order or otherwise. This may include market abuse activities or other prohibited activities as referred to in Section 14 of these Trading Rules, but may also include operational or otherwise abusive or adverse activities, such as using the API in a manner which unreasonably burdens the Bitvavo Trading Platform;
(ii) in case an Order is made in violation of any applicable law or regulation, these Trading Rules or the User Agreement or of principles of orderly and fair trading
(iii) in case of Orders which involve an error with respect to price, quantity, or other parameters;
(iv) if required by any applicable law or regulation;
(v) upon instruction of competent authorities or court order; or
(vi) if required for technical reasons.
15.2 Suspension of Account
Bitvavo may suspend or block specific or all use of an Account, suspend or cancel any pending Order or RfQ (including any requests to modify or cancel an Order), any transaction, suspend or cancel any deposit or withdrawal, freeze the Funds or Digital Assets related to an Account or suspend the cancellation of an Account in connection with an investigation into misuse of an Account or any Service provided by Bitvavo. If the legitimacy of any Participant or any Order, RfQ or use of the Services cannot be established, such Participant may lose all rights to the Funds and Digital Assets in its Account.
15.3 Delisting
Bitvavo may at any time and in its sole discretion decide to delist Digital Assets from the Bitvavo Trading Platform. Bitvavo can do so in any circumstances, including, but not limited to:
(a) a breach of these Trading Rules by the Issuer or non-conformity of the relevant Digital Asset with these Trading Rules;
(b) any events or developments regarding the Issuer or the Digital Asset that could pose material risk to the Participants or orderly trading on the Bitvavo Trading Platform;
(c) upon the request of a supervisory authority;
(d) in case of bankruptcy of the Issuer;
(e) if the Digital Asset is outside of the risk appetite of Bitvavo;
(f) upon the substantiated request of the Issuer of the Digital Asset;
(g) in case of material changes to the Issuer or the Digital Asset;
(h) the Digital Asset fails to meet pre-set minimum liquidity thresholds; or
(i) the Digital Asset does not comply with Section 3.5 of these Trading Rules.
15.4 Consequences of Delisting
Upon delisting of a Digital Asset, trading in the Digital Assets concerned will be discontinued. Bitvavo will, where possible, timely inform of any (planned) delisting arrangements and be given the opportunity to divest or trade-away Digital Assets that are subject to delisting.
16 Cooperation with supervisory authorities
16.1 Instructions from supervisory authorities
Bitvavo shall comply with instructions from supervisory authorities, including EBA and the AFM, which may result in suspension or delisting of Digital Assets.
16.2 Access to Information
Bitvavo shall comply with requests from supervisory authorities to provide relevant data relating to Orders in Digital Assets that are advertised through its systems, or to provide access to the Order Book, or to records of transactions executed on the Bitvavo Trading Platform. Relevant data may include details of any Order or transaction, as the case may be, including personal data and other datapoints that link Orders with transactions executed on the Bitvavo Trading Platform.
17 Fees and expenses
17.1 Fees for admitting to trading on Bitvavo Trading Platform
Bitvavo may charge fees for the admission to trading on the Bitvavo Trading Platform as well as periodic fees in order to remain listed and available for trading on the Bitvavo Trading Platform.
17.2 Fees for trading on the Bitvavo Trading Platform
(a) Participant shall be due fees to Bitvavo for trading on the Bitvavo Trading Platform.
(b) Any fees and the relevant fee amounts shall be published by Bitvavo on the designated fee information pages on the Website and/or the Bitvavo Environment (the Fee schedule), as amended from time to time, or shall be made available to Participant otherwise. Bitvavo may make changes hereto in its sole discretion from time to time. Any changes made available to Participants shall become effective directly.
17.3 Trading Fee Structure
(a) Trading fees on the Bitvavo Trading Platform are based on each Participant's trading volume from the previous 30 days in accordance with the Fee Schedule as published on the Bitvavo website from time to time.
(b) The total fee amount that is charged for a trade depends on the following:
(i) the total cost (value) of the Order;
(ii) the currency pair that is being traded;
(iii) the 30-day trading volume of the participant; and
(iv) whether an Order is maker or taker.
17.4 Calculation of the Fees
(a) The fee is charged (and rebates are given) in the quote asset.
(b) Fees are calculated for each fill.
(c) Fees are rounded up, to the precision of the asset.
(d) Fees are averaged for each Order. This means that if one fill has paid more in fees than required, the next fill pays a lower fee, so that the average fee paid equals or exceeds the fee tier the Participant is in. This process may be conducted manually after the settlement has been done.
(e) The 30-day rolling volume used to determine the fee tier is calculated in EUR, at 00:00 UTC each day.
(f) All Participants pay the fees mentioned in the Fees Schedule.
(g) Bitvavo may temporarily increase or decrease the fee tier for Market Makers and large institutions (determined on a case-by-case basis).
17.5 Payment of Fees
Bitvavo may charge any fees and costs to the Participant, including but not limited to trading fees, by deducting these from Participantās Funds, Digital Assets or Bitvavo E-Token Wallet.
18 Amendments to the Trading Rules
Bitvavo reserves the right to amend, add, or remove parts of the Trading Rules at any time and in its sole discretion. Participant will be notified of any changes and although Bitvavo will endeavour to provide Participant with advance notice, Bitvavo may indicate that the revised Trading Rules shall be effective immediately. If Participant does not agree with any such modification, Participant must close its Bitvavo Account and cease using the Bitvavo Trading Platform. If Participant continues to use the Bitvavo Trading Platform after a modification, Participant is deemed to have accepted and agreed to the amendments. It is the Participant's responsibility to review the amended Trading Rules.
Market | Min amount | Min amount quote | Max amount | Max amount quote | Max open orders | Tick size |
|---|---|---|---|---|---|---|
| 0G-EUR | 33.74954 0G | ā¬5 | 67,499,083.56558 0G | ā¬10,000,000 | 100 | 0.0000100 |
| 1INCH-EUR | 67.46985 1INCH | ā¬5 | 13,493,970,941.92902 1INCH | ā¬1,000,000,000 | 100 | 0.0000010 |
| 2Z-EUR | 210.76574 2Z | ā¬5 | 421,531,485.04448 2Z | ā¬10,000,000 | 100 | 0.0000010 |
| AAVE-EUR | 0.0442 AAVE | ā¬5 | 8,839,073.10312 AAVE | ā¬1,000,000,000 | 100 | 0.0100 |
| ACE-EUR | 43.11415 ACE | ā¬5 | 8,622,830,902.84251 ACE | ā¬1,000,000,000 | 100 | 0.0000100 |
| ACH-EUR | 1,180.87147 ACH | ā¬5 | 92,233,720,368.54776 ACH | ā¬1,000,000,000 | 100 | 0.0000001 |
| ACT-EUR | 688.17848 ACT | ā¬5 | 137,635,695,465.02707 ACT | ā¬1,000,000,000 | 100 | 0.00000100 |
| ACU-EUR | 44.43007 ACU | ā¬5 | 88,860,139.24322 ACU | ā¬10,000,000 | 100 | 0.0000100 |
| ADA-USDC | 25.71844 ADA | ā¬5 | 5,143,688,046.12065 ADA | ā¬1,000,000,000 | 100 | 0.0000100 |
| ADX-EUR | 107.23721 ADX | ā¬5 | 21,447,441,647.24419 ADX | ā¬1,000,000,000 | 100 | 0.00000100 |
| AERO-EUR | 9.09679 AERO | ā¬5 | 1,819,357,477.05166 AERO | ā¬1,000,000,000 | 100 | 0.0000100 |
| AEVO-EUR | 264.9178 AEVO | ā¬5 | 52,983,560,817.29469 AEVO | ā¬1,000,000,000 | 100 | 0.00000100 |
| AGI-EUR | 1,249.58803 AGI | ā¬5 | 92,233,720,368.54776 AGI | ā¬1,000,000,000 | 100 | 0.00000100 |
| AGLD-EUR | 31.52449 AGLD | ā¬5 | 6,304,897,524.32471 AGLD | ā¬1,000,000,000 | 100 | 0.0000100 |
| AI-EUR | 334.1131 AI | ā¬5 | 668,226,217.3223 AI | ā¬10,000,000 | 100 | 0.00000100 |
| AIOZ-EUR | 59.33131 AIOZ | ā¬5 | 11,866,262,681.76135 AIOZ | ā¬1,000,000,000 | 100 | 0.0000010 |
| AIXBT-EUR | 337.58332 AIXBT | ā¬5 | 67,516,664,248.08459 AIXBT | ā¬1,000,000,000 | 100 | 0.00000100 |
| AKT-EUR | 8.87135 AKT | ā¬5 | 1,774,269,970.64904 AKT | ā¬1,000,000,000 | 100 | 0.0000100 |
| ALGO-EUR | 59.01986 ALGO | ā¬5 | 11,803,971,096.05407 ALGO | ā¬1,000,000,000 | 100 | 0.0000010 |
| ALICE-EUR | 43.18055 ALICE | ā¬5 | 8,636,110,414.34731 ALICE | ā¬1,000,000,000 | 100 | 0.0000100 |
| ALIGN-EUR | 1,408.8934 ALIGN | ā¬5 | 2,817,786,805.5638 ALIGN | ā¬10,000,000 | 100 | 0.00000100 |
| ALLO-EUR | 31.091 ALLO | ā¬5 | 62,181,938.4906 ALLO | ā¬10,000,000 | 100 | 0.00000100 |
| ALT-EUR | 918.827 ALT | ā¬5 | 183,765,472,865.184 ALT | ā¬1,000,000,000 | 100 | 0.00000010 |
| AMP-EUR | 8,833.293 AMP | ā¬5 | 1,766,658,610,872.21 AMP | ā¬1,000,000,000 | 100 | 0.000000100 |
| ANIME-EUR | 2,021.19386 ANIME | ā¬5 | 92,233,720,368.54776 ANIME | ā¬1,000,000,000 | 100 | 0.00000010 |
| ANKR-EUR | 1,489.49449 ANKR | ā¬5 | 92,233,720,368.54776 ANKR | ā¬1,000,000,000 | 100 | 0.00000010 |
| APE-EUR | 48.79934 APE | ā¬5 | 9,759,868,868.08727 APE | ā¬1,000,000,000 | 100 | 0.0000100 |
| API3-EUR | 24.1787 API3 | ā¬5 | 4,835,739,728.127 API3 | ā¬1,000,000,000 | 100 | 0.0000100 |
| APT-EUR | 8.93702 APT | ā¬5 | 1,787,404,522.04115 APT | ā¬1,000,000,000 | 100 | 0.000100 |
| ARB-EUR | 33.887 ARB | ā¬5 | 6,777,399,792.37504 ARB | ā¬1,000,000,000 | 100 | 0.0000100 |
| ARK-EUR | 33.70933 ARK | ā¬5 | 6,741,866,586.2161 ARK | ā¬1,000,000,000 | 100 | 0.0000100 |
| ARKM-EUR | 51.80213 ARKM | ā¬5 | 10,360,426,749.30373 ARKM | ā¬1,000,000,000 | 100 | 0.0000100 |
| ARPA-EUR | 588.4206 ARPA | ā¬5 | 92,233,720,368.54776 ARPA | ā¬1,000,000,000 | 100 | 0.00000010 |
| ARX-EUR | 24.16794 ARX | ā¬5 | 48,335,881.72695 ARX | ā¬10,000,000 | 100 | 0.0000100 |
| ASTER-EUR | 8.39723 ASTER | ā¬5 | 16,794,455.94754 ASTER | ā¬10,000,000 | 100 | 0.0000100 |
| ASTR-EUR | 927.52072 ASTR | ā¬5 | 92,233,720,368.54776 ASTR | ā¬1,000,000,000 | 100 | 0.00000010 |
| ATH-EUR | 1,080.48534 ATH | ā¬5 | 92,233,720,368.54776 ATH | ā¬1,000,000,000 | 100 | 0.0000001 |
| ATOM-EUR | 3.69674 ATOM | ā¬5 | 739,346,971.31746 ATOM | ā¬1,000,000,000 | 100 | 0.000100 |
| AUCTION-EUR | 1.72309 AUCTION | ā¬5 | 344,618,385.28368 AUCTION | ā¬1,000,000,000 | 100 | 0.00010 |
| AUDIO-EUR | 429.20162 AUDIO | ā¬5 | 85,840,323,662.18274 AUDIO | ā¬1,000,000,000 | 100 | 0.0000010 |
| AVA-EUR | 16.66466 AVA | ā¬5 | 3,332,931,907.01134 AVA | ā¬1,000,000,000 | 100 | 0.0000100 |
| AVAX-EUR | 0.65595 AVAX | ā¬5 | 131,189,906.16127 AVAX | ā¬1,000,000,000 | 200 | 0.00010 |
| AVNT-EUR | 59.16907 AVNT | ā¬5 | 118,338,136.84261 AVNT | ā¬10,000,000 | 100 | 0.0000100 |
| AXIS-EUR | 41.5271 AXIS | ā¬5 | 83,054,271.4206 AXIS | ā¬10,000,000 | 100 | 0.00000100 |
| AXL-EUR | 131.32409 AXL | ā¬5 | 26,264,818,201.31794 AXL | ā¬1,000,000,000 | 100 | 0.0000010 |
| AXS-EUR | 6.75789 AXS | ā¬5 | 1,351,578,671.35543 AXS | ā¬1,000,000,000 | 100 | 0.000100 |
| AZTEC-EUR | 384.02831 AZTEC | ā¬5 | 768,056,626.54527 AZTEC | ā¬10,000,000 | 100 | 0.0000010 |
| BABY-EUR | 448.44895 BABY | ā¬5 | 89,689,790,975.33115 BABY | ā¬1,000,000,000 | 100 | 0.00000100 |
| BANANA-EUR | 1.81179 BANANA | ā¬5 | 362,357,802.70911 BANANA | ā¬1,000,000,000 | 100 | 0.00010 |
| BAND-EUR | 29.61116 BAND | ā¬5 | 5,922,232,492.10956 BAND | ā¬1,000,000,000 | 100 | 0.0000100 |
| BAT-EUR | 42.90713 BAT | ā¬5 | 8,581,425,451.60159 BAT | ā¬1,000,000,000 | 100 | 0.0000100 |
| BCH-EUR | 0.02042 BCH | ā¬5 | 4,083,338.82026 BCH | ā¬1,000,000,000 | 100 | 0.0100 |
| BEAM-EUR | 1,111.959 BEAM | ā¬5 | 222,391,794,888.86 BEAM | ā¬1,000,000,000 | 100 | 0.0000001 |
| BEL-EUR | 58.40438 BEL | ā¬5 | 11,680,875,431.11295 BEL | ā¬1,000,000,000 | 100 | 0.0000010 |
| BICO-EUR | 343.47265 BICO | ā¬5 | 68,694,529,526.83687 BICO | ā¬1,000,000,000 | 100 | 0.00000100 |
| BIGTIME-EUR | 886.44025 BIGTIME | ā¬5 | 92,233,720,368.54776 BIGTIME | ā¬1,000,000,000 | 100 | 0.0000010 |
| BILL-EUR | 1,037.6617 BILL | ā¬5 | 2,075,323,406.8956 BILL | ā¬10,000,000 | 100 | 0.00000100 |
| BIO-EUR | 266.97703 BIO | ā¬5 | 53,395,406,489.3247 BIO | ā¬1,000,000,000 | 100 | 0.0000010 |
| BIRB-EUR | 75.8414 BIRB | ā¬5 | 151,682,799.92151 BIRB | ā¬10,000,000 | 100 | 0.0000100 |
| BLEND-EUR | 111.46235 BLEND | ā¬5 | 222,924,695.08409 BLEND | ā¬10,000,000 | 100 | 0.0000100 |
| BLUR-EUR | 674.2432 BLUR | ā¬5 | 92,233,720,368.54776 BLUR | ā¬1,000,000,000 | 100 | 0.0000010 |
| BNB-EUR | 0.008 BNB | ā¬5 | 1,600,983.96735 BNB | ā¬1,000,000,000 | 100 | 0.0100 |
| BNT-EUR | 19.61861 BNT | ā¬5 | 3,923,721,114.78613 BNT | ā¬1,000,000,000 | 100 | 0.0000100 |
| BOB-EUR | 1,312.7368 BOB | ā¬5 | 2,625,473,601.149 BOB | ā¬10,000,000 | 100 | 0.00000010 |
| BOME-EUR | 9,051.8688 BOME | ā¬5 | 1,810,373,760,448.381 BOME | ā¬1,000,000,000 | 100 | 0.00000001 |
| BONK-EUR | 1,901,857 BONK | ā¬5 | 380,371,397,560,876 BONK | ā¬1,000,000,000 | 100 | 0.0000000001 |
| BRETT-EUR | 1,293.04011 BRETT | ā¬5 | 92,233,720,368.54776 BRETT | ā¬1,000,000,000 | 100 | 0.0000001 |
| BREV-EUR | 66.12024 BREV | ā¬5 | 132,240,470.26511 BREV | ā¬10,000,000 | 100 | 0.0000100 |
| BTC-USDC | 0.00006 BTC | ā¬5 | 12,650.73859 BTC | ā¬1,000,000,000 | 100 | 1.00 |
| BTT-EUR | 15,816,992 BTT | ā¬5 | 3,163,398,429,189,736 BTT | ā¬1,000,000,000 | 100 | 0.00000000001 |
| C-EUR | 77.1811 C | ā¬5 | 154,362,280.3181 C | ā¬10,000,000 | 100 | 0.00000100 |
| C98-EUR | 430.03416 C98 | ā¬5 | 86,006,831,564.64716 C98 | ā¬1,000,000,000 | 100 | 0.00000100 |
| CAKE-EUR | 3.01916 CAKE | ā¬5 | 603,831,389.63982 CAKE | ā¬1,000,000,000 | 100 | 0.000100 |
| CAP-EUR | 67.779 CAP | ā¬5 | 135,558,808.022 CAP | ā¬10,000,000 | 100 | 0.000000100 |
| CARV-EUR | 176.04499 CARV | ā¬5 | 352,089,973.9041 CARV | ā¬10,000,000 | 100 | 0.0000010 |
| CAT-EUR | 3,463,620 CAT | ā¬5 | 692,723,988,850,671 CAT | ā¬1,000,000,000 | 100 | 0.000000000100 |
| CATI-EUR | 140.05121 CATI | ā¬5 | 28,010,241,185.71347 CATI | ā¬1,000,000,000 | 100 | 0.0000010 |
| CC-EUR | 58.8148 CC | ā¬5 | 117,629,604.53359 CC | ā¬10,000,000 | 100 | 0.0000100 |
| CELO-EUR | 78.48308 CELO | ā¬5 | 15,696,616,728.71482 CELO | ā¬1,000,000,000 | 100 | 0.0000010 |
| CELR-EUR | 2,297.645 CELR | ā¬5 | 459,529,028,990.333 CELR | ā¬1,000,000,000 | 100 | 0.000000100 |
| CETUS-EUR | 273.80118 CETUS | ā¬5 | 54,760,235,850.36569 CETUS | ā¬1,000,000,000 | 100 | 0.0000010 |
| CFG-EUR | 65.83213 CFG | ā¬5 | 13,166,425,068.50152 CFG | ā¬1,000,000,000 | 100 | 0.0000010 |
| CHILLGUY-EUR | 647.15427 CHILLGUY | ā¬5 | 92,233,720,368.54776 CHILLGUY | ā¬1,000,000,000 | 100 | 0.0000001 |
| CHIP-EUR | 131.7608 CHIP | ā¬5 | 263,521,671.7638 CHIP | ā¬10,000,000 | 100 | 0.00000100 |
| CHR-EUR | 352.23699 CHR | ā¬5 | 70,447,398,124.92657 CHR | ā¬1,000,000,000 | 100 | 0.00000100 |
| CHZ-EUR | 449.70636 CHZ | ā¬5 | 89,941,272,427.30661 CHZ | ā¬1,000,000,000 | 100 | 0.00000100 |
| CNPY-EUR | 27.91048 CNPY | ā¬5 | 55,820,959.00699 CNPY | ā¬10,000,000 | 100 | 0.0000100 |
| COMP-EUR | 0.28754 COMP | ā¬5 | 57,507,021.86666 COMP | ā¬1,000,000,000 | 100 | 0.00100 |
| COTI-EUR | 584.86427 COTI | ā¬5 | 92,233,720,368.54776 COTI | ā¬1,000,000,000 | 100 | 0.00000100 |
| COW-EUR | 52.47381 COW | ā¬5 | 10,494,761,352.19633 COW | ā¬1,000,000,000 | 100 | 0.0000100 |
| CPOOL-EUR | 208.71803 CPOOL | ā¬5 | 41,743,605,800.38707 CPOOL | ā¬1,000,000,000 | 100 | 0.0000010 |
| CRO-EUR | 109.00892 CRO | ā¬5 | 21,801,784,804.14834 CRO | ā¬1,000,000,000 | 100 | 0.00000100 |
| CROSS-EUR | 52.53733 CROSS | ā¬5 | 105,074,657.26017 CROSS | ā¬10,000,000 | 100 | 0.0000010 |
| CRV-EUR | 19.97309 CRV | ā¬5 | 3,994,617,044.03786 CRV | ā¬1,000,000,000 | 100 | 0.0000100 |
| CSPR-EUR | 2,662.959 CSPR | ā¬5 | 532,591,881,440.743 CSPR | ā¬1,000,000,000 | 100 | 0.000000100 |
| CT-EUR | 43.11651 CT | ā¬5 | 86,233,019.00358 CT | ā¬10,000,000 | 100 | 0.0000100 |
| CTC-EUR | 59.20284 CTC | ā¬5 | 11,840,567,585.11412 CTC | ā¬1,000,000,000 | 100 | 0.0000100 |
| CTK-EUR | 65.65645 CTK | ā¬5 | 13,131,289,906.06992 CTK | ā¬1,000,000,000 | 100 | 0.0000100 |
| CTR-EUR | 391.4671 CTR | ā¬5 | 782,934,103.3495 CTR | ā¬10,000,000 | 100 | 0.00000100 |
| CTSI-EUR | 206.59309 CTSI | ā¬5 | 41,318,617,309.27635 CTSI | ā¬1,000,000,000 | 100 | 0.00000100 |
| CVC-EUR | 267.35215 CVC | ā¬5 | 53,470,429,995.92419 CVC | ā¬1,000,000,000 | 100 | 0.0000010 |
| CVX-EUR | 3.00123 CVX | ā¬5 | 600,245,132.39465 CVX | ā¬1,000,000,000 | 100 | 0.000100 |
| CYBER-EUR | 20.64651 CYBER | ā¬5 | 4,129,302,419.6765 CYBER | ā¬1,000,000,000 | 100 | 0.0000100 |
| DATAIP-EUR | 43.11432 DATAIP | ā¬5 | 86,228,647.04881 DATAIP | ā¬10,000,000 | 100 | 0.000100 |
| DBR-EUR | 416.03593 DBR | ā¬5 | 83,207,185,228.42963 DBR | ā¬1,000,000,000 | 100 | 0.0000010 |
| DEEP-EUR | 355.74999 DEEP | ā¬5 | 71,149,998,715.12753 DEEP | ā¬1,000,000,000 | 100 | 0.00000100 |
| DEGEN-EUR | 6,445.653 DEGEN | ā¬5 | 1,289,130,603,047.047 DEGEN | ā¬1,000,000,000 | 100 | 0.000000010 |
| DGB-EUR | 1,769.864 DGB | ā¬5 | 353,972,885,369.443 DGB | ā¬1,000,000,000 | 100 | 0.0000001 |
| DIA-EUR | 42.9353 DIA | ā¬5 | 8,587,059,030.31517 DIA | ā¬1,000,000,000 | 100 | 0.0000100 |
| DODO-EUR | 236.57341 DODO | ā¬5 | 47,314,682,443.23177 DODO | ā¬1,000,000,000 | 100 | 0.00000100 |
| DOGE-EUR | 75.37906 DOGE | ā¬5 | 15,075,812,568.61159 DOGE | ā¬1,000,000,000 | 100 | 0.0000010 |
| DOGS-EUR | 174,470.26 DOGS | ā¬5 | 34,894,051,088,147.54 DOGS | ā¬1,000,000,000 | 100 | 0.0000000010 |
| DOS-EUR | 29.306 DOS | ā¬5 | 58,612,006.30102 DOS | ā¬10,000,000 | 100 | 0.0000100 |
| DOT-EUR | 6.12254 DOT | ā¬5 | 1,224,507,760.98016 DOT | ā¬1,000,000,000 | 100 | 0.000100 |
| DRIFT-EUR | 431.74125 DRIFT | ā¬5 | 86,348,250,554.56003 DRIFT | ā¬1,000,000,000 | 100 | 0.0000010 |
| DRV-EUR | 16.93921 DRV | ā¬5 | 33,878,429.52085 DRV | ā¬10,000,000 | 100 | 0.0000100 |
| DUSK-EUR | 59.25174 DUSK | ā¬5 | 11,850,347,099.52247 DUSK | ā¬1,000,000,000 | 100 | 0.0000010 |
| DYDX-EUR | 52.67593 DYDX | ā¬5 | 10,535,185,940.63324 DYDX | ā¬1,000,000,000 | 100 | 0.0000100 |
| DYM-EUR | 355.62619 DYM | ā¬5 | 71,125,237,587.41028 DYM | ā¬1,000,000,000 | 100 | 0.0000010 |
| EDEN-EUR | 109.8656 EDEN | ā¬5 | 219,731,180.8897 EDEN | ā¬10,000,000 | 100 | 0.00000100 |
| EDGE-EUR | 67.82869 EDGE | ā¬5 | 135,657,373.9338 EDGE | ā¬10,000,000 | 100 | 0.0000010 |
| EDU-EUR | 105.08042 EDU | ā¬5 | 21,016,083,447.64827 EDU | ā¬1,000,000,000 | 100 | 0.0000100 |
| EGLD-EUR | 1.73746 EGLD | ā¬5 | 347,492,567.30099 EGLD | ā¬1,000,000,000 | 100 | 0.00010 |
| EIGEN-EUR | 33.90842 EIGEN | ā¬5 | 6,781,683,738.97066 EIGEN | ā¬1,000,000,000 | 100 | 0.0000100 |
| ELSA-EUR | 87.55721 ELSA | ā¬5 | 175,114,429.21967 ELSA | ā¬10,000,000 | 100 | 0.0000010 |
| ENA-EUR | 29.61898 ENA | ā¬5 | 5,923,796,516.1071 ENA | ā¬1,000,000,000 | 100 | 0.0000100 |
| ENJ-EUR | 236.7873 ENJ | ā¬5 | 47,357,459,643.7141 ENJ | ā¬1,000,000,000 | 100 | 0.0000010 |
| ENS-EUR | 1.20584 ENS | ā¬5 | 241,168,096.24693 ENS | ā¬1,000,000,000 | 100 | 0.00010 |
| ENSO-EUR | 9.54156 ENSO | ā¬5 | 19,083,125.24621 ENSO | ā¬10,000,000 | 100 | 0.000100 |
| EPIC-EUR | 52.66573 EPIC | ā¬5 | 10,533,146,608.58814 EPIC | ā¬1,000,000,000 | 100 | 0.000010 |
| ESP-EUR | 67.74092 ESP | ā¬5 | 135,481,831.03088 ESP | ā¬10,000,000 | 100 | 0.0000010 |
| ETC-EUR | 0.78521 ETC | ā¬5 | 157,041,828.50037 ETC | ā¬1,000,000,000 | 100 | 0.00010 |
| ETH-EUR | 0.00244 ETH | ā¬5 | 487,965.30009 ETH | ā¬1,000,000,000 | 100 | 0.010 |
| ETHFI-EUR | 9.57715 ETHFI | ā¬5 | 1,915,429,815.35079 ETHFI | ā¬1,000,000,000 | 100 | 0.0000100 |
| EUL-EUR | 5.30568 EUL | ā¬5 | 10,611,363.68341 EUL | ā¬10,000,000 | 100 | 0.000010 |
| EURC-USDC | 4.29387 EURC | ā¬5 | 8,587,745.28748 EURC | ā¬10,000,000 | 100 | 0.0001000 |
| EURCV-EUR | 5 EURCV | ā¬5 | 10,000,000 EURCV | ā¬10,000,000 | 100 | 0.000100 |
| EUROP-EUR | 4.81025 EUROP | ā¬5 | 962,050,313.38542 EUROP | ā¬1,000,000,000 | 100 | 0.000100 |
| F-EUR | 1,962.93695 F | ā¬5 | 92,233,720,368.54776 F | ā¬1,000,000,000 | 100 | 0.0000001 |
| FARTCOIN-EUR | 47.31729 FARTCOIN | ā¬5 | 94,634,586.8473 FARTCOIN | ā¬10,000,000 | 100 | 0.0000100 |
| FET-EUR | 33.91569 FET | ā¬5 | 6,783,138,848.17338 FET | ā¬1,000,000,000 | 200 | 0.0000100 |
| FIDA-EUR | 340.66926 FIDA | ā¬5 | 68,133,852,678.21864 FIDA | ā¬1,000,000,000 | 100 | 0.00000100 |
| FIL-EUR | 6.75524 FIL | ā¬5 | 1,351,047,469.26873 FIL | ā¬1,000,000,000 | 100 | 0.000010 |
| FLOCK-EUR | 152.67785 FLOCK | ā¬5 | 305,355,703.68333 FLOCK | ā¬10,000,000 | 100 | 0.0000010 |
| FLOKI-EUR | 238,393 FLOKI | ā¬5 | 47,678,556,366,826 FLOKI | ā¬1,000,000,000 | 100 | 0.0000000010 |
| FLR-EUR | 942.69816 FLR | ā¬5 | 92,233,720,368.54776 FLR | ā¬1,000,000,000 | 100 | 0.00000010 |
| FLUID-EUR | 3.03822 FLUID | ā¬5 | 6,076,446.92596 FLUID | ā¬10,000,000 | 100 | 0.000100 |
| FLUX-EUR | 94.54798 FLUX | ā¬5 | 18,909,595,680.36708 FLUX | ā¬1,000,000,000 | 100 | 0.0000010 |
| FOLD-EUR | 118.6816 FOLD | ā¬5 | 237,363,122.4339 FOLD | ā¬10,000,000 | 100 | 0.00000100 |
| FORM-EUR | 27.29023 FORM | ā¬5 | 5,458,045,789.01743 FORM | ā¬1,000,000,000 | 100 | 0.000010 |
| FRAX-EUR | 21.88264 FRAX | ā¬5 | 43,765,279.78137 FRAX | ā¬10,000,000 | 100 | 0.0000100 |
| FTT-EUR | 25.0028 FTT | ā¬5 | 5,000,559,823.43868 FTT | ā¬1,000,000,000 | 100 | 0.0000100 |
| FUEL-EUR | 6,790.911 FUEL | ā¬5 | 1,358,182,158,152.148 FUEL | ā¬1,000,000,000 | 100 | 0.0000001 |
| FUN-EUR | 419.96926 FUN | ā¬5 | 839,938,517.91192 FUN | ā¬10,000,000 | 100 | 0.0000010 |
| G-EUR | 1,701.70096 G | ā¬5 | 92,233,720,368.54776 G | ā¬1,000,000,000 | 100 | 0.00000010 |
| GALA-EUR | 3,360.95784 GALA | ā¬5 | 92,233,720,368.54776 GALA | ā¬1,000,000,000 | 100 | 0.0000001 |
| GAS-EUR | 5.05593 GAS | ā¬5 | 1,011,186,884.247 GAS | ā¬1,000,000,000 | 100 | 0.000100 |
| GIGA-EUR | 3,177.57108 GIGA | ā¬5 | 92,233,720,368.54776 GIGA | ā¬1,000,000,000 | 100 | 0.0000001 |
| GLM-EUR | 52.52533 GLM | ā¬5 | 10,505,065,836.78947 GLM | ā¬1,000,000,000 | 100 | 0.0000100 |
| GLMR-EUR | 731.32339 GLMR | ā¬5 | 92,233,720,368.54776 GLMR | ā¬1,000,000,000 | 100 | 0.0000010 |
| GMT-EUR | 856.43436 GMT | ā¬5 | 92,233,720,368.54776 GMT | ā¬1,000,000,000 | 100 | 0.00000100 |
| GMX-EUR | 0.70854 GMX | ā¬5 | 141,708,384.14367 GMX | ā¬1,000,000,000 | 100 | 0.00010 |
| GNO-EUR | 0.05115 GNO | ā¬5 | 10,229,824.95364 GNO | ā¬1,000,000,000 | 100 | 0.0100 |
| GNS-EUR | 14.80715 GNS | ā¬5 | 2,961,430,436.2441 GNS | ā¬1,000,000,000 | 100 | 0.000010 |
| GOAT-EUR | 414.73486 GOAT | ā¬5 | 82,946,971,267.77208 GOAT | ā¬1,000,000,000 | 100 | 0.00000100 |
| GRAM-EUR | 4.73523 GRAM | ā¬5 | 9,470,452.50779 GRAM | ā¬10,000,000 | 100 | 0.000100 |
| GRASS-EUR | 9.46557 GRASS | ā¬5 | 1,893,114,440.56991 GRASS | ā¬1,000,000,000 | 100 | 0.000010 |
| GROVE-EUR | 780.6661 GROVE | ā¬5 | 1,561,332,118.0315 GROVE | ā¬10,000,000 | 100 | 0.00000100 |
| GRT-EUR | 283.71266 GRT | ā¬5 | 56,742,531,945.04549 GRT | ā¬1,000,000,000 | 100 | 0.00000100 |
| GTC-EUR | 25.9073 GTC | ā¬5 | 5,181,460,113.35772 GTC | ā¬1,000,000,000 | 100 | 0.0000010 |
| GWEI-EUR | 272.5456 GWEI | ā¬5 | 545,091,298.041 GWEI | ā¬10,000,000 | 100 | 0.00000100 |
| HAEDAL-EUR | 235.51013 HAEDAL | ā¬5 | 471,020,261.456 HAEDAL | ā¬10,000,000 | 100 | 0.0000010 |
| HBAR-EUR | 78.31133 HBAR | ā¬5 | 15,662,266,527.41751 HBAR | ā¬1,000,000,000 | 200 | 0.0000010 |
| HEI-EUR | 52.78326 HEI | ā¬5 | 10,556,652,590.06099 HEI | ā¬1,000,000,000 | 100 | 0.0000010 |
| HFT-EUR | 1,130.46978 HFT | ā¬5 | 92,233,720,368.54776 HFT | ā¬1,000,000,000 | 100 | 0.00000100 |
| HMSTR-EUR | 40,498.295 HMSTR | ā¬5 | 8,099,659,061,107.227 HMSTR | ā¬1,000,000,000 | 100 | 0.000000010 |
| HNT-EUR | 15.25425 HNT | ā¬5 | 3,050,850,459.95966 HNT | ā¬1,000,000,000 | 100 | 0.000010 |
| HOME-EUR | 1,072.6522 HOME | ā¬5 | 2,145,304,415.4102 HOME | ā¬10,000,000 | 100 | 0.00000100 |
| HOT-EUR | 16,647.89 HOT | ā¬5 | 3,329,578,167,721.31 HOT | ā¬1,000,000,000 | 100 | 0.0000000100 |
| HUMA-EUR | 192.9256 HUMA | ā¬5 | 385,851,239.1023 HUMA | ā¬10,000,000 | 100 | 0.00000100 |
| HYPE-EUR | 0.06008 HYPE | ā¬5 | 12,016,401.50568 HYPE | ā¬1,000,000,000 | 200 | 0.00100 |
| ICNT-EUR | 29.20418 ICNT | ā¬5 | 58,408,363.78262 ICNT | ā¬10,000,000 | 100 | 0.0000100 |
| ICP-EUR | 2.29994 ICP | ā¬5 | 459,987,485.97133 ICP | ā¬1,000,000,000 | 100 | 0.000100 |
| ID-EUR | 197.5472 ID | ā¬5 | 39,509,439,046.17334 ID | ā¬1,000,000,000 | 100 | 0.0000010 |
| IKA-EUR | 3,993.828 IKA | ā¬5 | 7,987,656,013.1681 IKA | ā¬10,000,000 | 100 | 0.00000010 |
| ILV-EUR | 1.92298 ILV | ā¬5 | 384,596,807.18222 ILV | ā¬1,000,000,000 | 100 | 0.00010 |
| IMU-EUR | 3,444.005 IMU | ā¬5 | 6,888,010,299.859 IMU | ā¬10,000,000 | 100 | 0.000000100 |
| IMX-EUR | 47.17973 IMX | ā¬5 | 9,435,946,724.15027 IMX | ā¬1,000,000,000 | 100 | 0.0000100 |
| INIT-EUR | 26.29574 INIT | ā¬5 | 52,591,488.81035 INIT | ā¬10,000,000 | 100 | 0.0000010 |
| INJ-EUR | 0.79313 INJ | ā¬5 | 158,626,913.15635 INJ | ā¬1,000,000,000 | 100 | 0.000100 |
| INX-EUR | 1,339.2845 INX | ā¬5 | 2,678,569,036.261 INX | ā¬10,000,000 | 100 | 0.00000100 |
| IO-EUR | 43.03505 IO | ā¬5 | 8,607,010,675.88802 IO | ā¬1,000,000,000 | 100 | 0.0000100 |
| IOST-EUR | 7,823.7295 IOST | ā¬5 | 1,564,745,892,445.8435 IOST | ā¬1,000,000,000 | 100 | 0.000000100 |
| IQ-EUR | 7,568.632 IQ | ā¬5 | 1,513,726,451,563.466 IQ | ā¬1,000,000,000 | 100 | 0.000000100 |
| IRYS-EUR | 264.9981 IRYS | ā¬5 | 529,996,150.0738 IRYS | ā¬10,000,000 | 100 | 0.00000100 |
| JASMY-EUR | 1,494.244 JASMY | ā¬5 | 298,848,791,805.693 JASMY | ā¬1,000,000,000 | 100 | 0.0000001 |
| JTO-EUR | 15.7014 JTO | ā¬5 | 3,140,273,046.7757 JTO | ā¬1,000,000,000 | 100 | 0.000010 |
| JUP-EUR | 23.216 JUP | ā¬5 | 4,643,106,425.971 JUP | ā¬1,000,000,000 | 100 | 0.0000100 |
| KAIA-EUR | 175.86878 KAIA | ā¬5 | 35,173,756,891.06276 KAIA | ā¬1,000,000,000 | 100 | 0.00000100 |
| KAITO-EUR | 23.74322 KAITO | ā¬5 | 4,748,643,853.97007 KAITO | ā¬1,000,000,000 | 100 | 0.0000100 |
| KAS-EUR | 156.57656 KAS | ā¬5 | 31,315,312,987.93035 KAS | ā¬1,000,000,000 | 100 | 0.0000010 |
| KAT-EUR | 1,357.1132 KAT | ā¬5 | 2,714,226,347.3089 KAT | ā¬10,000,000 | 100 | 0.00000100 |
| KERNEL-EUR | 115.46175 KERNEL | ā¬5 | 23,092,349,022.3343 KERNEL | ā¬1,000,000,000 | 100 | 0.0000010 |
| KITE-EUR | 52.2033 KITE | ā¬5 | 104,406,507.1989 KITE | ā¬10,000,000 | 100 | 0.00001000 |
| KMNO-EUR | 157.43973 KMNO | ā¬5 | 31,487,945,308.64268 KMNO | ā¬1,000,000,000 | 100 | 0.0000010 |
| KNC-EUR | 47.46631 KNC | ā¬5 | 9,493,262,988.96814 KNC | ā¬1,000,000,000 | 100 | 0.0000100 |
| KSM-EUR | 1.61219 KSM | ā¬5 | 322,438,722.75277 KSM | ā¬1,000,000,000 | 100 | 0.00010 |
| LAPTOP-EUR | 116.5564 LAPTOP | ā¬5 | 233,112,805.91929 LAPTOP | ā¬10,000,000 | 100 | 0.0000100 |
| LAYER-EUR | 94.7098 LAYER | ā¬5 | 189,419,599.66664 LAYER | ā¬10,000,000 | 100 | 0.0000010 |
| LDO-EUR | 16.95669 LDO | ā¬5 | 3,391,337,083.50735 LDO | ā¬1,000,000,000 | 100 | 0.0000100 |
| LIGHTER-EUR | 2.01245 LIGHTER | ā¬5 | 4,024,897.71676 LIGHTER | ā¬10,000,000 | 100 | 0.000100 |
| LINEA-EUR | 2,398.2464 LINEA | ā¬5 | 4,796,492,746.9463 LINEA | ā¬10,000,000 | 100 | 0.00000010 |
| LINK-EUR | 0.51185 LINK | ā¬5 | 102,369,223.94122 LINK | ā¬1,000,000,000 | 100 | 0.00010 |
| LISTA-EUR | 75.02292 LISTA | ā¬5 | 15,004,583,437.10635 LISTA | ā¬1,000,000,000 | 100 | 0.0000010 |
| LMWR-EUR | 627.79842 LMWR | ā¬5 | 92,233,720,368.54776 LMWR | ā¬1,000,000,000 | 100 | 0.0000010 |
| LPT-EUR | 4.10616 LPT | ā¬5 | 821,232,995.72699 LPT | ā¬1,000,000,000 | 100 | 0.000100 |
| LQTY-EUR | 30.91471 LQTY | ā¬5 | 6,182,942,578.61353 LQTY | ā¬1,000,000,000 | 100 | 0.0000100 |
| LRC-EUR | 728.84673 LRC | ā¬5 | 92,233,720,368.54776 LRC | ā¬1,000,000,000 | 100 | 0.000001 |
| LSK-EUR | 26.35178 LSK | ā¬5 | 5,270,356,941.66381 LSK | ā¬1,000,000,000 | 100 | 0.0000100 |
| LTC-EUR | 0.10142 LTC | ā¬5 | 20,284,666.25241 LTC | ā¬1,000,000,000 | 100 | 0.00100 |
| LUMIA-EUR | 67.48765 LUMIA | ā¬5 | 13,497,530,392.19255 LUMIA | ā¬1,000,000,000 | 100 | 0.0000010 |
| LUNA-EUR | 130,801.58203 LUNA | ā¬5 | 9,223,372,036,854.775 LUNA | ā¬1,000,000,000 | 100 | 0.0000000010 |
| LUNA2-EUR | 142.43752 LUNA2 | ā¬5 | 28,487,504,241.25016 LUNA2 | ā¬1,000,000,000 | 100 | 0.0000010 |
| MAGIC-EUR | 67.08809 MAGIC | ā¬5 | 13,417,617,690.38107 MAGIC | ā¬1,000,000,000 | 100 | 0.00000100 |
| MANA-EUR | 77.2976 MANA | ā¬5 | 15,459,519,044.10315 MANA | ā¬1,000,000,000 | 100 | 0.000001 |
| MANTA-EUR | 94.6456 MANTA | ā¬5 | 18,929,120,728.223 MANTA | ā¬1,000,000,000 | 100 | 0.000001 |
| MANTRA-EUR | 1,649.6084 MANTRA | ā¬5 | 3,299,216,798.7617 MANTRA | ā¬10,000,000 | 100 | 0.00000100 |
| MASK-EUR | 15.3 MASK | ā¬5 | 3,060,000,820.84012 MASK | ā¬1,000,000,000 | 100 | 0.0000100 |
| MAV-EUR | 638.10753 MAV | ā¬5 | 92,233,720,368.54776 MAV | ā¬1,000,000,000 | 100 | 0.00000100 |
| MAVIA-EUR | 236.31267 MAVIA | ā¬5 | 47,262,533,110.88154 MAVIA | ā¬1,000,000,000 | 100 | 0.0000010 |
| ME-EUR | 93.9866 ME | ā¬5 | 18,797,320,455.56612 ME | ā¬1,000,000,000 | 100 | 0.000010 |
| MEGA-EUR | 118.39293 MEGA | ā¬5 | 236,785,865.52228 MEGA | ā¬10,000,000 | 100 | 0.0000100 |
| MEME-EUR | 12,925.66 MEME | ā¬5 | 2,585,132,010,389.95 MEME | ā¬1,000,000,000 | 100 | 0.000000010 |
| MERL-EUR | 198.25212 MERL | ā¬5 | 39,650,424,522.92683 MERL | ā¬1,000,000,000 | 100 | 0.0000010 |
| MET-EUR | 21.17822 MET | ā¬5 | 42,356,442.04409 MET | ā¬10,000,000 | 100 | 0.0000100 |
| METIS-EUR | 2.00018 METIS | ā¬5 | 400,036,899.77306 METIS | ā¬1,000,000,000 | 100 | 0.00010 |
| MEW-EUR | 13,638.02 MEW | ā¬5 | 2,727,603,905,863.485 MEW | ā¬1,000,000,000 | 100 | 0.000000010 |
| MIOTA-EUR | 143.35553 MIOTA | ā¬5 | 28,671,105,289.68378 MIOTA | ā¬1,000,000,000 | 100 | 0.0000010 |
| MIRA-EUR | 138.47197 MIRA | ā¬5 | 276,943,936.97172 MIRA | ā¬10,000,000 | 100 | 0.0000010 |
| MLN-EUR | 4.25 MLN | ā¬5 | 849,999,541.54197 MLN | ā¬1,000,000,000 | 100 | 0.000100 |
| MMT-EUR | 43.80152 MMT | ā¬5 | 87,603,047.62687 MMT | ā¬10,000,000 | 100 | 0.0000100 |
| MOCA-EUR | 686.91713 MOCA | ā¬5 | 92,233,720,368.54776 MOCA | ā¬1,000,000,000 | 100 | 0.0000010 |
| MOG-EUR | 59,207,288 MOG | ā¬5 | 11,841,457,513,169,568 MOG | ā¬1,000,000,000 | 100 | 0.000000000010 |
| MON-EUR | 285.499 MON | ā¬5 | 570,998,063.912 MON | ā¬10,000,000 | 100 | 0.00000100 |
| MOODENG-EUR | 158.18325 MOODENG | ā¬5 | 31,636,650,235.6426 MOODENG | ā¬1,000,000,000 | 100 | 0.00000100 |
| MORPHO-EUR | 2.70155 MORPHO | ā¬5 | 540,310,734.96752 MORPHO | ā¬1,000,000,000 | 100 | 0.000010 |
| MOVE-EUR | 925.99064 MOVE | ā¬5 | 92,233,720,368.54776 MOVE | ā¬1,000,000,000 | 100 | 0.0000010 |
| MOVR-EUR | 5.49172 MOVR | ā¬5 | 1,098,344,351.22167 MOVR | ā¬1,000,000,000 | 100 | 0.000100 |
| MTL-EUR | 22.11442 MTL | ā¬5 | 4,422,883,776.67344 MTL | ā¬1,000,000,000 | 100 | 0.0000100 |
| NEAR-EUR | 1.341 NEAR | ā¬5 | 268,199,818.43193 NEAR | ā¬1,000,000,000 | 100 | 0.000100 |
| NEIRO-EUR | 88,020.07 NEIRO | ā¬5 | 17,604,013,414,285.57 NEIRO | ā¬1,000,000,000 | 100 | 0.0000000010 |
| NEO-EUR | 2.85786 NEO | ā¬5 | 571,572,823.10036 NEO | ā¬1,000,000,000 | 100 | 0.000100 |
| NES-EUR | 47.78808 NES | ā¬5 | 95,576,168.60724 NES | ā¬10,000,000 | 100 | 0.0000100 |
| NEWT-EUR | 131.63678 NEWT | ā¬5 | 263,273,569.48191 NEWT | ā¬10,000,000 | 100 | 0.0000010 |
| NEX-EUR | 8,228,507.6 NEX | ā¬5 | 16,457,015,255,126.9 NEX | ā¬10,000,000 | 100 | 0.00000000010 |
| NIL-EUR | 75.30934 NIL | ā¬5 | 15,061,868,295.24463 NIL | ā¬1,000,000,000 | 100 | 0.0000010 |
| NMR-EUR | 0.61696 NMR | ā¬5 | 123,391,754.691 NMR | ā¬1,000,000,000 | 100 | 0.000100 |
| NOM-EUR | 3,565.5193 NOM | ā¬5 | 7,131,038,624.0709 NOM | ā¬10,000,000 | 100 | 0.00000010 |
| NOS-EUR | 13.95865 NOS | ā¬5 | 2,791,729,557.9912 NOS | ā¬1,000,000,000 | 100 | 0.000010 |
| NOT-EUR | 15,818.301 NOT | ā¬5 | 3,163,660,210,377.248 NOT | ā¬1,000,000,000 | 100 | 0.000000010 |
| NPC-EUR | 367.159 NPC | ā¬5 | 73,431,845,085.137 NPC | ā¬1,000,000,000 | 100 | 0.00000010 |
| O-EUR | 13.48167 O | ā¬5 | 26,963,346.35904 O | ā¬10,000,000 | 100 | 0.0000100 |
| OGN-EUR | 232.17604 OGN | ā¬5 | 46,435,208,942.16338 OGN | ā¬1,000,000,000 | 100 | 0.0000010 |
| ONDO-EUR | 14.70111 ONDO | ā¬5 | 2,940,222,809.16404 ONDO | ā¬1,000,000,000 | 100 | 0.0000100 |
| OP-EUR | 52.67361 OP | ā¬5 | 10,534,721,818.82628 OP | ā¬1,000,000,000 | 100 | 0.000010 |
| OPEN-EUR | 66.13531 OPEN | ā¬5 | 132,270,628.03923 OPEN | ā¬10,000,000 | 100 | 0.0000100 |
| ORCA-EUR | 3.40735 ORCA | ā¬5 | 681,469,609.206 ORCA | ā¬1,000,000,000 | 100 | 0.000010 |
| OSMO-EUR | 117.953 OSMO | ā¬5 | 23,590,599,188.20141 OSMO | ā¬1,000,000,000 | 100 | 0.0000010 |
| PARTI-EUR | 106.63565 PARTI | ā¬5 | 21,327,130,336.7129 PARTI | ā¬1,000,000,000 | 100 | 0.0000010 |
| PEAQ-EUR | 175.55192 PEAQ | ā¬5 | 35,110,384,519.38837 PEAQ | ā¬1,000,000,000 | 100 | 0.0000010 |
| PENDLE-EUR | 3.32597 PENDLE | ā¬5 | 665,193,641.78165 PENDLE | ā¬1,000,000,000 | 100 | 0.000100 |
| PENGU-EUR | 776.514 PENGU | ā¬5 | 155,302,895,195.046 PENGU | ā¬1,000,000,000 | 100 | 0.000000100 |
| PEOPLE-EUR | 808.10105 PEOPLE | ā¬5 | 92,233,720,368.54776 PEOPLE | ā¬1,000,000,000 | 100 | 0.0000001 |
| PEPE-EUR | 1,094,699 PEPE | ā¬5 | 218,939,773,231,012 PEPE | ā¬1,000,000,000 | 100 | 0.000000000100 |
| PHA-EUR | 135.22799 PHA | ā¬5 | 27,045,597,011.92357 PHA | ā¬1,000,000,000 | 100 | 0.0000010 |
| PIXEL-EUR | 1,296.52687 PIXEL | ā¬5 | 92,233,720,368.54776 PIXEL | ā¬1,000,000,000 | 100 | 0.0000001 |
| PLUME-EUR | 376.16255 PLUME | ā¬5 | 75,232,509,277.312 PLUME | ā¬1,000,000,000 | 100 | 0.0000001 |
| PNT-EUR | 178.5992 PNT | ā¬5 | 357,198,472.558 PNT | ā¬10,000,000 | 100 | 0.00000100 |
| PNUT-EUR | 143.67933 PNUT | ā¬5 | 28,735,864,960.31715 PNUT | ā¬1,000,000,000 | 100 | 0.0000010 |
| POL-EUR | 66.15093 POL | ā¬5 | 13,230,186,962.57056 POL | ā¬1,000,000,000 | 100 | 0.0000010 |
| POND-EUR | 4,646.774 POND | ā¬5 | 929,354,762,393.87 POND | ā¬1,000,000,000 | 100 | 0.00000010 |
| PONKE-EUR | 332.14598 PONKE | ā¬5 | 66,429,195,714.39938 PONKE | ā¬1,000,000,000 | 100 | 0.0000010 |
| POPCAT-EUR | 142.74979 POPCAT | ā¬5 | 28,549,957,449.41066 POPCAT | ā¬1,000,000,000 | 100 | 0.0000010 |
| PORTAL-EUR | 447.20237 PORTAL | ā¬5 | 89,440,474,763.66687 PORTAL | ā¬1,000,000,000 | 100 | 0.00000100 |
| POWR-EUR | 106.98535 POWR | ā¬5 | 21,397,069,910.97275 POWR | ā¬1,000,000,000 | 100 | 0.0000010 |
| PROM-EUR | 0.99754 PROM | ā¬5 | 199,507,882.08424 PROM | ā¬1,000,000,000 | 100 | 0.000100 |
| PROMPT-EUR | 347.6977 PROMPT | ā¬5 | 695,395,425.5305 PROMPT | ā¬10,000,000 | 100 | 0.0000010 |
| PROVE-EUR | 29.1836 PROVE | ā¬5 | 58,367,202.50506 PROVE | ā¬10,000,000 | 100 | 0.0000100 |
| PTB-EUR | 48,275.05 PTB | ā¬5 | 96,550,100,740.55 PTB | ā¬10,000,000 | 100 | 0.000000100 |
| PUFFER-EUR | 201.4267 PUFFER | ā¬5 | 40,285,339,898.92738 PUFFER | ā¬1,000,000,000 | 100 | 0.0000010 |
| PUMP-EUR | 1,390.005 PUMP | ā¬5 | 2,780,009,080.191 PUMP | ā¬10,000,000 | 100 | 0.000000100 |
| PUNDIX-EUR | 51.01426 PUNDIX | ā¬5 | 10,202,852,311.11838 PUNDIX | ā¬1,000,000,000 | 100 | 0.0000100 |
| PYTH-EUR | 91.93885 PYTH | ā¬5 | 18,387,769,420.00374 PYTH | ā¬1,000,000,000 | 100 | 0.0000010 |
| QKC-EUR | 2,378.012 QKC | ā¬5 | 475,602,304,749.366 QKC | ā¬1,000,000,000 | 100 | 0.000000100 |
| QNT-EUR | 0.02903 QNT | ā¬5 | 5,806,175.27855 QNT | ā¬1,000,000,000 | 200 | 0.00100 |
| QUID-EUR | 94.7079 QUID | ā¬5 | 189,415,792.7009 QUID | ā¬10,000,000 | 100 | 0.00000100 |
| RAD-EUR | 24.97562 RAD | ā¬5 | 4,995,123,146.71104 RAD | ā¬1,000,000,000 | 100 | 0.0000100 |
| RARE-EUR | 466.2304 RARE | ā¬5 | 92,233,720,368.54776 RARE | ā¬1,000,000,000 | 100 | 0.00000100 |
| RAY-EUR | 3.4967 RAY | ā¬5 | 699,332,470.06 RAY | ā¬1,000,000,000 | 100 | 0.000010 |
| RE-EUR | 15.7765 RE | ā¬5 | 31,552,995.92383 RE | ā¬10,000,000 | 100 | 0.0000100 |
| RECALL-EUR | 157.61162 RECALL | ā¬5 | 315,223,234.26768 RECALL | ā¬10,000,000 | 100 | 0.0000010 |
| RED-EUR | 47.4263 RED | ā¬5 | 9,485,259,031.48173 RED | ā¬1,000,000,000 | 100 | 0.0000100 |
| RENDER-EUR | 3.57783 RENDER | ā¬5 | 715,565,934.43361 RENDER | ā¬1,000,000,000 | 100 | 0.000100 |
| REQ-EUR | 111.80557 REQ | ā¬5 | 22,361,114,016.30215 REQ | ā¬1,000,000,000 | 100 | 0.0000010 |
| REZ-EUR | 1,350.12129 REZ | ā¬5 | 92,233,720,368.54776 REZ | ā¬1,000,000,000 | 100 | 0.0000001 |
| RLC-EUR | 10.95627 RLC | ā¬5 | 2,191,253,536.69069 RLC | ā¬1,000,000,000 | 100 | 0.000010 |
| ROBO-EUR | 1,109.2886 ROBO | ā¬5 | 2,218,577,236.2523 ROBO | ā¬10,000,000 | 100 | 0.00000100 |
| RON-EUR | 112.15939 RON | ā¬5 | 22,431,877,279.11123 RON | ā¬1,000,000,000 | 100 | 0.0000010 |
| ROSE-EUR | 914.79607 ROSE | ā¬5 | 92,233,720,368.54776 ROSE | ā¬1,000,000,000 | 100 | 0.0000010 |
| RPL-EUR | 3.72842 RPL | ā¬5 | 745,683,869.20018 RPL | ā¬1,000,000,000 | 100 | 0.000100 |
| RSR-EUR | 4,078.3265 RSR | ā¬5 | 815,665,303,591.3488 RSR | ā¬1,000,000,000 | 100 | 0.0000001 |
| RUNE-EUR | 8.40492 RUNE | ā¬5 | 1,680,984,328.8452 RUNE | ā¬1,000,000,000 | 100 | 0.000010 |
| S-EUR | 133.88621 S | ā¬5 | 26,777,241,368.57679 S | ā¬1,000,000,000 | 100 | 0.0000010 |
| SAFE-EUR | 65.73935 SAFE | ā¬5 | 13,147,869,115.64969 SAFE | ā¬1,000,000,000 | 100 | 0.0000010 |
| SAGA-EUR | 328.12607 SAGA | ā¬5 | 65,625,213,688.55223 SAGA | ā¬1,000,000,000 | 100 | 0.0000010 |
| SAND-EUR | 118.39347 SAND | ā¬5 | 23,678,694,308.05334 SAND | ā¬1,000,000,000 | 100 | 0.0000010 |
| SAPIEN-EUR | 109.50445 SAPIEN | ā¬5 | 219,008,892.51953 SAPIEN | ā¬10,000,000 | 100 | 0.0000010 |
| SCR-EUR | 279.42305 SCR | ā¬5 | 55,884,610,323.93161 SCR | ā¬1,000,000,000 | 100 | 0.0000010 |
| SEI-EUR | 116.6479 SEI | ā¬5 | 23,329,579,320.57068 SEI | ā¬1,000,000,000 | 100 | 0.0000010 |
| SENT-EUR | 300.2645 SENT | ā¬5 | 600,528,921.5606 SENT | ā¬10,000,000 | 100 | 0.00000100 |
| SFP-EUR | 26.39357 SFP | ā¬5 | 5,278,714,974.29877 SFP | ā¬1,000,000,000 | 100 | 0.0000100 |
| SHELL-EUR | 221.8407 SHELL | ā¬5 | 443,681,444.1146 SHELL | ā¬10,000,000 | 100 | 0.0000010 |
| SHIB-EUR | 1,181,736.86 SHIB | ā¬5 | 236,347,371,867,631.03 SHIB | ā¬1,000,000,000 | 100 | 0.0000000001 |
| SIGN-EUR | 545.6428 SIGN | ā¬5 | 1,091,285,628.8142 SIGN | ā¬10,000,000 | 100 | 0.00000100 |
| SKL-EUR | 1,456.08128 SKL | ā¬5 | 92,233,720,368.54776 SKL | ā¬1,000,000,000 | 100 | 0.0000001 |
| SKY-EUR | 87.6047 SKY | ā¬5 | 175,209,333.8445 SKY | ā¬10,000,000 | 100 | 0.00000100 |
| SLP-EUR | 11,272.5974 SLP | ā¬5 | 2,254,519,471,672.9287 SLP | ā¬1,000,000,000 | 100 | 0.000000010 |
| SLX-EUR | 118.70001 SLX | ā¬5 | 237,400,028.07912 SLX | ā¬10,000,000 | 100 | 0.0000100 |
| SNX-EUR | 30.93948 SNX | ā¬5 | 6,187,895,706.71288 SNX | ā¬1,000,000,000 | 100 | 0.0000100 |
| SOL-EUR | 0.05687 SOL | ā¬5 | 11,374,900.67965 SOL | ā¬1,000,000,000 | 200 | 0.0010 |
| SOLV-EUR | 1,088.1782 SOLV | ā¬5 | 2,176,356,333.2357 SOLV | ā¬10,000,000 | 100 | 0.00000010 |
| SOMI-EUR | 29.65001 SOMI | ā¬5 | 59,300,010.48908 SOMI | ā¬10,000,000 | 100 | 0.0000100 |
| SOON-EUR | 17.65251 SOON | ā¬5 | 35,305,024.20344 SOON | ā¬10,000,000 | 100 | 0.0000100 |
| SOSO-EUR | 18.8264 SOSO | ā¬5 | 37,652,805.50187 SOSO | ā¬10,000,000 | 100 | 0.0000100 |
| SPK-EUR | 325.6607 SPK | ā¬5 | 651,321,412.9947 SPK | ā¬10,000,000 | 100 | 0.00000100 |
| SPX-EUR | 15.80392 SPX | ā¬5 | 3,160,783,463.51916 SPX | ā¬1,000,000,000 | 100 | 0.0000100 |
| SQD-EUR | 296.35793 SQD | ā¬5 | 592,715,865.63373 SQD | ā¬10,000,000 | 100 | 0.0000010 |
| SSV-EUR | 2.41078 SSV | ā¬5 | 482,156,396.42386 SSV | ā¬1,000,000,000 | 100 | 0.000100 |
| STO-EUR | 186.34657 STO | ā¬5 | 372,693,132.54572 STO | ā¬10,000,000 | 100 | 0.0000010 |
| STRAX-EUR | 554.96507 STRAX | ā¬5 | 92,233,720,368.54776 STRAX | ā¬1,000,000,000 | 100 | 0.00000100 |
| STRK-EUR | 132.33268 STRK | ā¬5 | 26,466,536,233.86363 STRK | ā¬1,000,000,000 | 100 | 0.0000010 |
| STX-EUR | 19.78678 STX | ā¬5 | 3,957,356,855.06577 STX | ā¬1,000,000,000 | 100 | 0.0000100 |
| SUI-USDC | 5.6822 SUI | ā¬5 | 1,136,439,493.29743 SUI | ā¬1,000,000,000 | 100 | 0.00001 |
| SUPER-EUR | 35.95605 SUPER | ā¬5 | 7,191,210,604.11257 SUPER | ā¬1,000,000,000 | 100 | 0.0000100 |
| SUSHI-EUR | 29.40467 SUSHI | ā¬5 | 5,880,933,233.1693 SUSHI | ā¬1,000,000,000 | 100 | 0.0000100 |
| SWELL-EUR | 7,839.1764 SWELL | ā¬5 | 1,567,835,273,244.504 SWELL | ā¬1,000,000,000 | 100 | 0.00000010 |
| SXT-EUR | 707.7892 SXT | ā¬5 | 1,415,578,379.6832 SXT | ā¬10,000,000 | 100 | 0.00000100 |
| SYN-EUR | 35.03681 SYN | ā¬5 | 7,007,361,952.2587 SYN | ā¬1,000,000,000 | 100 | 0.0000010 |
| SYRUP-EUR | 37.97942 SYRUP | ā¬5 | 7,595,883,886.34327 SYRUP | ā¬1,000,000,000 | 100 | 0.0000100 |
| T-EUR | 1,258.58506 T | ā¬5 | 92,233,720,368.54776 T | ā¬1,000,000,000 | 100 | 0.0000001 |
| TAI-EUR | 1,813.93281 TAI | ā¬5 | 92,233,720,368.54776 TAI | ā¬1,000,000,000 | 100 | 0.0000010 |
| TAIKO-EUR | 75.738 TAIKO | ā¬5 | 15,147,599,695.40549 TAIKO | ā¬1,000,000,000 | 100 | 0.00001 |
| TAO-EUR | 0.02371 TAO | ā¬5 | 4,742,829.89821 TAO | ā¬1,000,000,000 | 200 | 0.0100 |
| THE-EUR | 118.31426 THE | ā¬5 | 23,662,851,875.89254 THE | ā¬1,000,000,000 | 100 | 0.0000100 |
| THQ-EUR | 557.2657 THQ | ā¬5 | 1,114,531,442.8007 THQ | ā¬10,000,000 | 100 | 0.00000100 |
| TIA-EUR | 12.17802 TIA | ā¬5 | 2,435,603,766.66083 TIA | ā¬1,000,000,000 | 100 | 0.000010 |
| TLM-EUR | 4,472.7135 TLM | ā¬5 | 894,542,707,303.9456 TLM | ā¬1,000,000,000 | 100 | 0.000000100 |
| TNSR-EUR | 200.15572 TNSR | ā¬5 | 40,031,143,588.69408 TNSR | ā¬1,000,000,000 | 100 | 0.0000010 |
| TOSHI-EUR | 53,367.83 TOSHI | ā¬5 | 106,735,660,642.4 TOSHI | ā¬10,000,000 | 100 | 0.0000000100 |
| TOWNS-EUR | 4,269.6452 TOWNS | ā¬5 | 8,539,290,405.9893 TOWNS | ā¬10,000,000 | 100 | 0.00000010 |
| TRAC-EUR | 16.4238 TRAC | ā¬5 | 3,284,760,855.10073 TRAC | ā¬1,000,000,000 | 100 | 0.0000100 |
| TRB-EUR | 0.35257 TRB | ā¬5 | 70,514,662.02766 TRB | ā¬1,000,000,000 | 100 | 0.00100 |
| TREAD-EUR | 7.54138 TREAD | ā¬5 | 15,082,765.44758 TREAD | ā¬10,000,000 | 100 | 0.0000100 |
| TREE-EUR | 158.0434 TREE | ā¬5 | 316,086,802.99127 TREE | ā¬10,000,000 | 100 | 0.0000010 |
| TRIA-EUR | 2,246.615 TRIA | ā¬5 | 4,493,229,951.9382 TRIA | ā¬10,000,000 | 100 | 0.00000100 |
| TRUMP-EUR | 3.56679 TRUMP | ā¬5 | 713,358,739.68605 TRUMP | ā¬1,000,000,000 | 100 | 0.000100 |
| TRUST-EUR | 112.00468 TRUST | ā¬5 | 224,009,368.17232 TRUST | ā¬10,000,000 | 100 | 0.0000010 |
| TRX-EUR | 16.36035 TRX | ā¬5 | 3,272,069,485.33716 TRX | ā¬1,000,000,000 | 100 | 0.0000100 |
| TURBO-EUR | 7,293.181 TURBO | ā¬5 | 1,458,636,238,510.125 TURBO | ā¬1,000,000,000 | 100 | 0.000000100 |
| TWT-EUR | 13.58405 TWT | ā¬5 | 2,716,810,658.4708 TWT | ā¬1,000,000,000 | 100 | 0.0000100 |
| U-EUR | 53,678.0027 U | ā¬5 | 107,356,005,495.9573 U | ā¬10,000,000 | 100 | 0.00000010 |
| UMA-EUR | 17.77997 UMA | ā¬5 | 3,555,993,291.07636 UMA | ā¬1,000,000,000 | 100 | 0.000010 |
| UNI-EUR | 0.83414 UNI | ā¬5 | 166,828,884.3815 UNI | ā¬1,000,000,000 | 100 | 0.000100 |
| UP-EUR | 94.71693 UP | ā¬5 | 189,433,869.62307 UP | ā¬10,000,000 | 100 | 0.0000010 |
| USDC-EUR | 5.82842 USDC | ā¬5 | 1,165,683,218.59125 USDC | ā¬1,000,000,000 | 100 | 0.0001000 |
| USDCV-EUR | 5.81395 USDCV | ā¬5 | 11,627,906.977 USDCV | ā¬10,000,000 | 100 | 0.000010 |
| USELESS-EUR | 42.35869 USELESS | ā¬5 | 84,717,373.79771 USELESS | ā¬10,000,000 | 100 | 0.0000010 |
| VANA-EUR | 7.03391 VANA | ā¬5 | 1,406,781,177.93483 VANA | ā¬1,000,000,000 | 100 | 0.000100 |
| VELO-EUR | 1,630.4084 VELO | ā¬5 | 326,081,681,918.5737 VELO | ā¬1,000,000,000 | 100 | 0.00000010 |
| VERONA-EUR | 48.04361 VERONA | ā¬5 | 96,087,227.17474 VERONA | ā¬10,000,000 | 100 | 0.0000100 |
| VET-EUR | 965.13402 VET | ā¬5 | 92,233,720,368.54776 VET | ā¬1,000,000,000 | 100 | 0.00000010 |
| VIRTUAL-EUR | 9.80456 VIRTUAL | ā¬5 | 1,960,912,777.48033 VIRTUAL | ā¬1,000,000,000 | 100 | 0.0000100 |
| VSN-EUR | 148.3435 VSN | ā¬5 | 296,687,073.8465 VSN | ā¬10,000,000 | 100 | 0.00000100 |
| VTHO-EUR | 9,960.873 VTHO | ā¬5 | 1,992,174,560,463.492 VTHO | ā¬1,000,000,000 | 100 | 0.000000010 |
| VVV-EUR | 0.24382 VVV | ā¬5 | 487,639.28216 VVV | ā¬10,000,000 | 100 | 0.000100 |
| W-EUR | 468.06175 W | ā¬5 | 93,612,349,191.17728 W | ā¬1,000,000,000 | 100 | 0.00000100 |
| WAL-EUR | 183.42147 WAL | ā¬5 | 36,684,293,711.42107 WAL | ā¬1,000,000,000 | 100 | 0.0000010 |
| WAXP-EUR | 1,297.76821 WAXP | ā¬5 | 92,233,720,368.54776 WAXP | ā¬1,000,000,000 | 100 | 0.00000010 |
| WCT-EUR | 175.52666 WCT | ā¬5 | 35,105,331,976.12938 WCT | ā¬1,000,000,000 | 100 | 0.0000010 |
| WELL-EUR | 3,030.4461 WELL | ā¬5 | 92,233,720,368.54776 WELL | ā¬1,000,000,000 | 100 | 0.0000001 |
| WHUF-EUR | 2.94666 WHUF | ā¬5 | 5,893,313.82496 WHUF | ā¬10,000,000 | 100 | 0.000100 |
| WIF-EUR | 33.54169 WIF | ā¬5 | 6,708,338,181.37564 WIF | ā¬1,000,000,000 | 100 | 0.0000100 |
| WIN-EUR | 87,242.34044 WIN | ā¬5 | 9,223,372,036,854.775 WIN | ā¬1,000,000,000 | 100 | 0.0000000010 |
| WLD-EUR | 14.39108 WLD | ā¬5 | 2,878,215,331.81403 WLD | ā¬1,000,000,000 | 100 | 0.0000100 |
| WLFI-EUR | 110.92253 WLFI | ā¬5 | 221,845,051.98721 WLFI | ā¬10,000,000 | 100 | 0.0000100 |
| WMTX-EUR | 311.1372 WMTX | ā¬5 | 622,274,332.5964 WMTX | ā¬10,000,000 | 100 | 0.00000100 |
| WOO-EUR | 530.1827 WOO | ā¬5 | 92,233,720,368.54776 WOO | ā¬1,000,000,000 | 100 | 0.0000010 |
| XAI-EUR | 788.049 XAI | ā¬5 | 157,609,712,071.08 XAI | ā¬1,000,000,000 | 100 | 0.00000010 |
| XAN-EUR | 594.9427 XAN | ā¬5 | 1,189,885,414.6812 XAN | ā¬10,000,000 | 100 | 0.00000010 |
| XDC-EUR | 177.40584 XDC | ā¬5 | 35,481,168,353.80119 XDC | ā¬1,000,000,000 | 100 | 0.0000010 |
| XDP-EUR | 306.8059 XDP | ā¬5 | 613,611,881.0893 XDP | ā¬10,000,000 | 100 | 0.00000100 |
| XLM-EUR | 33.91225 XLM | ā¬5 | 6,782,449,341.13198 XLM | ā¬1,000,000,000 | 100 | 0.0000100 |
| XMN-EUR | 15,132.4864 XMN | ā¬5 | 30,264,972,774.0781 XMN | ā¬10,000,000 | 100 | 0.00000100 |
| XPL-EUR | 76.56017 XPL | ā¬5 | 153,120,339.97831 XPL | ā¬10,000,000 | 100 | 0.0000010 |
| XRP-EUR | 4.53363 XRP | ā¬5 | 906,726,135.77812 XRP | ā¬1,000,000,000 | 100 | 0.000010 |
| XTZ-EUR | 21.54981 XTZ | ā¬5 | 4,309,961,309.81928 XTZ | ā¬1,000,000,000 | 100 | 0.000010 |
| XVG-EUR | 2,465.05017 XVG | ā¬5 | 493,010,033,578.0179 XVG | ā¬1,000,000,000 | 100 | 0.000000100 |
| XYO-EUR | 1,875.978 XYO | ā¬5 | 375,195,660,311.432 XYO | ā¬1,000,000,000 | 100 | 0.000000100 |
| YB-EUR | 90.76327 YB | ā¬5 | 181,526,530.69868 YB | ā¬10,000,000 | 100 | 0.0000100 |
| YFI-EUR | 0.00306 YFI | ā¬5 | 611,103.56352 YFI | ā¬1,000,000,000 | 100 | 0.100 |
| YGG-EUR | 235.26294 YGG | ā¬5 | 47,052,588,645.46288 YGG | ā¬1,000,000,000 | 100 | 0.0000010 |
| ZAMA-EUR | 88.1697 ZAMA | ā¬5 | 176,339,326.7872 ZAMA | ā¬10,000,000 | 100 | 0.00000100 |
| ZBCN-EUR | 2,805.011 ZBCN | ā¬5 | 5,610,022,237.282 ZBCN | ā¬10,000,000 | 100 | 0.000000100 |
| ZBT-EUR | 79.03211 ZBT | ā¬5 | 158,064,227.86698 ZBT | ā¬10,000,000 | 100 | 0.0000010 |
| ZEN-EUR | 1.04165 ZEN | ā¬5 | 208,330,989.4891 ZEN | ā¬1,000,000,000 | 100 | 0.00010 |
| ZETA-EUR | 152.6825 ZETA | ā¬5 | 30,536,491,078.4781 ZETA | ā¬1,000,000,000 | 100 | 0.0000010 |
| ZEUS-EUR | 800.13186 ZEUS | ā¬5 | 92,233,720,368.54776 ZEUS | ā¬1,000,000,000 | 100 | 0.0000001 |
| ZIG-EUR | 135.9472 ZIG | ā¬5 | 271,894,440.6584 ZIG | ā¬10,000,000 | 100 | 0.00000100 |
| ZIL-EUR | 2,913.8846 ZIL | ā¬5 | 582,776,918,103.9 ZIL | ā¬1,000,000,000 | 100 | 0.00000010 |
| ZK-EUR | 541.0671 ZK | ā¬5 | 92,233,720,368.54776 ZK | ā¬1,000,000,000 | 100 | 0.0000010 |
| ZKC-EUR | 178.23345 ZKC | ā¬5 | 356,466,905.87923 ZKC | ā¬10,000,000 | 100 | 0.0000010 |
| ZKJ-EUR | 1,108.96367 ZKJ | ā¬5 | 92,233,720,368.54776 ZKJ | ā¬1,000,000,000 | 100 | 0.000001 |
| ZKP-EUR | 131.58606 ZKP | ā¬5 | 263,172,116.86042 ZKP | ā¬10,000,000 | 100 | 0.0000010 |
| ZORA-EUR | 925.8136 ZORA | ā¬5 | 1,851,627,227.033 ZORA | ā¬10,000,000 | 100 | 0.00000100 |
| ZRC-EUR | 4,547.09057 ZRC | ā¬5 | 92,233,720,368.54776 ZRC | ā¬1,000,000,000 | 100 | 0.0000001 |
| ZRO-EUR | 3.2399 ZRO | ā¬5 | 647,979,569.57457 ZRO | ā¬1,000,000,000 | 100 | 0.000100 |
| ZRX-EUR | 59.3535 ZRX | ā¬5 | 11,870,699,977.45814 ZRX | ā¬1,000,000,000 | 100 | 0.0000010 |
Bitvavo B.V.
Trading digital assets involves significant risks. Digital assets are highly volatile and you may lose some or all of your investment. The information on this page does not constitute advice, and should not be relied upon as such. Bitvavo is authorized as a crypto-asset service provider under Regulation (EU) 2023/1114 (MiCA) by the Autoriteit Financiƫle Markten (AFM), Vijzelgracht 50, 1017 HS Amsterdam. More info can be found in our Risk Disclosure.
Bitvavo is registered at the Dutch Chamber of Commerce, number 68743424.