| [Table 2] Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens | |||||
| Template for white papers for crypto-assets other than asset-referenced tokens or e-money tokens [abstract] | |||||
| General information | |||||
| 00 Table of content | boolean true | ||||
| 01 Date of notification | date | ||||
| 02 Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114 | boolean true | ||||
| 03 Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114 | boolean true | ||||
| 04 Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114 | boolean true | ||||
| 05 Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114 | boolean true | ||||
| 06 Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114 | boolean true | ||||
| SUMMARY | |||||
| 07 Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114 | boolean true | This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto –asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law. |
|||
| 08 Characteristics of the crypto-asset | textBlock | Key characteristics: - Token name: FutureChain Token (FTC) - Total supply: 1,000,000,000 FTC (one billion) - Smallest unit: 1 satoshi (0.00000001 FTC), 8 decimal places - Issuance: Exclusively through Proof of Work mining rewards - Transaction model: UTXO (Unspent Transaction Output) - Consensus: Proof of Work (SHA-256 double hash) - Block time: 15 seconds - Finality: ~100 confirmations (~25 minutes) - Transaction fees: 0.1% of amount (minimum 0.00002 FTC, maximum 0.1 FTC) - Fee distribution: 75% to miners, 25% to treasury FTC is NOT an E-Money Token (does not reference an official currency) and NOT an Asset-Referenced Token (does not reference other assets or values). FTC serves as the native utility token of the FutureChain network. |
|||
| 09 Further information about utility tokens | textBlock | 1. Transaction Fee Payment: FTC is used to pay transaction fees for processing payments on the FutureChain blockchain. Every transaction on the network requires a fee denominated in FTC. 2. Network Participation (Mining): FTC holders may participate in securing the network through Proof of Work mining. Miners who successfully validate blocks receive FTC as mining rewards. 3. Service Access: FTC enables access to FutureChain's compliance screening (Heimdall engine) and ISO 20022 PACS.008 payment integration services. The goods and services to which FTC provides access are currently operational. The FutureChain network has been in production since 2025, with 800,000+ blocks mined and demonstrated throughput of approximately 4.9 transactions per second steady-state with full compliance screening, up to approximately 110+ transactions per second peak burst. ISO 20022 PACS.008 messages are archived on Full and Archive node types; the chain has had native PACS.008.001.13 support since 2025. |
|||
| 10 Key information about the offer to the public or admission to trading | textBlock | Public offering: New FTC tokens are created exclusively as mining rewards. There is no direct sale by FutureChain AB. Any person with compatible mining hardware and software may participate. Admission to trading: FutureChain AB intends to seek admission of FTC to trading on MiCA-authorized platforms, initially targeting Swedish platforms such as Safello. FTC may subsequently be admitted to trading on additional platforms across the EU. There is no fundraising target, no subscription period, and no fixed issue price. FutureChain AB does not mainly raise funds through FTC distribution. The company's revenue model is based on B2B technology licensing. |
|||
| Part A - Information about offeror or person seeking admission to trading | |||||
| A.1 Name | text | ||||
| A.2 Legal form | text | ||||
| A.3 Registered address | |||||
| Registered addess | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.4 Head office | |||||
| Head office | text | ||||
| Country | enumeration | ||||
| Sub-division | text | ||||
| A.5 Registration date | date | ||||
| A.6 Legal entity identifier | LEI | ||||
| A.7 Another identifier required pursuant to applicable national law | text | ||||
| A.8 Contact telephone number | text | ||||
| A.9 E-mail address | text | ||||
| A.10 Response time (days) | integer | ||||
| A.11 Parent company | text | ||||
| A.12 Members of the management body | |||||
| Member #1 | id | 1 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| Member #2 | id | 2 | |||
| Identity | text | ||||
| Business address | text | ||||
| Function | text | ||||
| A.13 Business activity | textBlock | - Annual licensing fees based on transaction volume - Implementation and integration services - Ongoing support and compliance updates FutureChain AB does not operate as a crypto-asset service provider (CASP). Target customers include banks, payment service providers, electronic money institutions, central banks, and MiCA-authorized CASPs. |
|||
| A.14 Parent company business activity | textBlock | ||||
| A.15 Newly established | boolean | ||||
| A.16 Financial condition for the past three years | textBlock | ||||
| A.17 Financial condition since registration | textBlock | ||||
| Part B - Information about issuer, if different from offeror or person seeking admission to trading | |||||
| B.1 Issuer different from offerror or person seeking admission to trading | boolean | ||||
| B.2 Name | N/A | . | |||
| B.3 Legal form | N/A | . | |||
| B.4 Registered address | |||||
| Registered addess | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| B.5 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| B.6 Registration date | N/A | . | |||
| B.7 Legal entity identifier | N/A | . | |||
| B.8 Another identifier required pursuant to applicable national law | N/A | . | |||
| B.9 Parent company | N/A | . | |||
| B.10 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| B.11 Business activity | N/A | . | |||
| B.12 Parent company business activity | N/A | . | |||
| Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | |||||
| C.1 Name | N/A | . | |||
| C.2 Legal form | N/A | . | |||
| C.3 Registered address | |||||
| Registered address | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.4 Head office | |||||
| Head office | N/A | . | |||
| Country | N/A | . | |||
| Sub-division | N/A | . | |||
| C.5 Registration date | N/A | . | |||
| C.6 Legal entity identifier | N/A | . | |||
| C.7 Another identifier required pursuant to applicable national law | N/A | . | |||
| C.8 Parent company | N/A | . | |||
| C.9 Reason for crypto-asset white paper preparation | N/A | . | |||
| C.10 Members of the management body | |||||
| Member #1 | N/A | . | |||
| Identity | N/A | . | |||
| Business address | N/A | . | |||
| Function | N/A | . | |||
| C.11 Operator business activity | N/A | . | |||
| C.12 Parent company business activity | N/A | . | |||
| C.13 Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 | N/A | . | |||
| Part D - Information about other token project | |||||
| D.1 Crypto-asset project name | text | ||||
| D.2 Crypto-asset name | text | ||||
| D.3 Abbreviation | text | ||||
| D.4 Crypto-asset project description | textBlock | Key innovations (patent pending, Swedish PRV): 1. Pre-Transaction Compliance (Heimdall): A mandatory compliance gateway, enforced at the protocol level above block 360,000, screens every transaction before blockchain inclusion. Country-jurisdiction screening and sanctioned-wallet-address screening are in active enforcement (transactions are blocked); the remaining controls operate in shadow mode (log and alert) and are promoted to active enforcement under a documented graduation policy. Transactions without a valid compliance-node signature are refused at the gateway. 2. Two-Tier Storage: On-chain hashes + encrypted off-chain ISO 20022 data. Achieves reduction in storage reduction while preserving full regulatory data. GDPR-compatible. 3. Native ISO 20022: Built-in PACS.008.001.13 support enabling direct integration with existing banking systems. 4. Cryptographic Compliance Proofs: Every approved transaction carries an immutable compliance signature. Compliance-gateway signatures use a hybrid scheme combining classical Ed25519 with FALCON-512 (NIST FIPS 206 FN-DSA, post-quantum), making the compliance gate quantum-safe. Production status: Rust code, 800,000+ blocks mined, approximately 110 transactions per second depending on workload, >99.9% uptime. A public RPC endpoint (https://rpc.futurechain.eu) and a mainnet-isolated public testnet are operational. |
|||
| D.5 Details of all natural or legal persons involved in implementation of crypto-asset project | |||||
| Person #1 | id | 1 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| Person #2 | id | 2 | |||
| Type of person | enumeration | ||||
| Name of person | text | ||||
| Business address of person | text | ||||
| Domicile of company | enumeration | ||||
| D.6 Utility token classification | boolean | ||||
| D.7 Key features of goods or services for utility token projects | text | ||||
| D.8 Plans for the token | |||||
| Description of past milestones | textBlock | - Core blockchain implementation in Rust - ISO 20022 PACS.008.001.13 native integration - Heimdall compliance engine integration - Two-tier storage architecture (on-chain + encrypted off-chain) - Multi-node production network deployment - HSM/PKCS#11 integration for hardware key protection - P2P TLS 1.3 enforcement on all node communications - SIEM stack deployment (Prometheus/Grafana/Loki/Alertmanager) Additional milestones COMPLETE (May 2026): - Post-quantum compliance signatures: hybrid Ed25519 + FALCON-512 (NIST FIPS 206 FN-DSA) shipped to mainnet; approximately 250 hybrid signatures proven in production - HSM-backed compliance signer registry (SoftHSM2 via PKCS#11) - Activation-height enforcement gate deployed at block 810,000 (dormant until the chain mines through that height), at which point hybrid compliance signatures become mandatory - Public testnet launched (Network ID 5777, mainnet-isolated, 5 hybrid compliance signers) - Bahnhof public RPC endpoint (https://rpc.futurechain.eu) with bearer authentication, rate limiting, and signed-challenge enrollment - ANTON (mobile) wallet with envelope v3 storage and Play Integrity device attestation; ANTON (desktop); Anton Agent (desktop) with a Model Context Protocol server and a DESKTOP_V1 attestation primitive |
|||
| Description of future milestones | textBlock | - MiCA white paper notification to Finansinspektionen (target submission: 2026-06-02) - DTI code registration with DTIF (anchor: mainnet genesis block; submission made May 2026; code assignment pending) - Big4 external security audit engagement (audit package prepared and ready; engagement letter pending) - Promotion of additional Heimdall controls from shadow to active enforcement under the documented graduation policy - First commercial B2B technology licensing agreement Phase 3 (Q3-Q4 2026): - Full active-enforcement coverage across all Heimdall controls - External audit completion - First MiCA-authorised CASP admission to trading (target: Safello) - Cloud deployment templates (AWS, Azure, GCP) - Hardware wallet integration (Ledger, Trezor) - Additional ISO message types (PAIN.001) Phase 4 (2027+): - Private network deployments for enterprise clients - Central bank integration pilots - On-chain governance implementation Note: This roadmap is indicative and subject to change. |
|||
| D.9 Resource allocation | text | ||||
| D.10 Planned use of collected funds or other tokens | text | ||||
| Part E - Information about offer to public of other tokens or their admission to trading | |||||
| E.1 Public offering or admission to trading | enumeration | ||||
| E.2 Reasons for public offer or admission to trading | textBlock | 1. Network Security: FTC mining rewards incentivize participants to contribute computational resources to secure the FutureChain blockchain through Proof of Work consensus. 2. Network Utility: FTC serves as the transaction fee medium on the FutureChain network. A functioning token economy is essential for processing compliant cross-border payments. 3. Liquidity and Accessibility: Admission to trading on regulated platforms enables holders to acquire and dispose of FTC in a transparent, regulated environment with MiCA consumer protections. 4. Ecosystem Development: A distributed and liquid token supply is essential for the FutureChain ecosystem to serve regulated financial institutions across the European Union. |
|||
| E.3 Fundraising target | |||||
| Target expressed in currency | monetary | EUR | |||
| Target expressed in units | decimal | ||||
| Target expressed in digital token identifier | text | ||||
| E.4 Minimum subscription goals | |||||
| Goals expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.5 Maximum subscription goals | |||||
| Goasl expressed in currency | monetary | EUR | |||
| Goals expressed in units | decimal | ||||
| Goals expressed in digital token identifier | text | ||||
| E.6 Oversubscription acceptance | boolean | ||||
| E.7 Oversubscription allocation | text | ||||
| Issue price details | |||||
| E.8 Issue price | decimal | ||||
| E.9 Official currency determining issue price | enumeration | ||||
| E.9 Any other tokens determining issue price | text | ||||
| E.10 Subscription fee | |||||
| Fee expressed in currency | monetary | EUR | |||
| Fee expressed in units | decimal | ||||
| Fee expressed in digital token identifier | text | ||||
| E.11 Offer price determination method | text | ||||
| E.12 Total number of offered or traded other tokens | integer | ||||
| E.13 Targeted holders | enumeration | ||||
| E.14 Holder restrictions | text | ||||
| E.15 Reimbursement notice | boolean true | ||||
| E.16 Refund mechanism | textBlock | ||||
| E.17 Refund timeline | text | ||||
| E.18 Offer phases | textBlock | ||||
| E.19 Early purchase discount | textBlock | ||||
| E.20 Time-limited offer | boolean | ||||
| E.21 Subscription period beginning | date | ||||
| E.22 Subscription period end | date | ||||
| E.23 Safeguarding arrangements for offered funds or other tokens | textBlock | ||||
| E.24 Payment methods for other token purchase | textBlock | ||||
| E.25 Value transfer methods for reimbursement | textBlock | ||||
| E.26 Right of withdrawal | textBlock | ||||
| E.27 Transfer of purchased other tokens | textBlock | ||||
| E.28 Transfer time schedule | text | ||||
| E.29 Purchaser's technical requirements | textBlock | ||||
| Other token services provider characteristics | |||||
| E.30 Other token service provider (CASP) name | text | ||||
| E.31 CASP identifier | LEI | ||||
| E.32 Placement form | enumeration | ||||
| Trading platforms characteristics | |||||
| E.33 Trading platforms name | text | ||||
| E.34 Trading platforms market identifier code (MIC) | text | ||||
| E.35 Trading platforms access | text | ||||
| E.36 Involved costs | textBlock | ||||
| E.37 Offer expenses | textBlock | ||||
| E.38 Conflicts of interest | textBlock | ||||
| E.39 Applicable law | textBlock | ||||
| E.40 Competent court | textBlock | ||||
| Part F - Information about other tokens | |||||
| F.1 Crypto-asset type | text | ||||
| F.2 Other token functionality | textBlock | ||||
| F.3 Planned application of functionalities | textBlock | ||||
| A description of the characteristics of the other token, including the data necessary for classification of the crypto-asset white paper in the register referred to in Article 109 of Regulation (EU) 2023/1114, as specified in accordance with paragraph 8 of that Article | |||||
| F.4 Type of crypto-asset white paper | enumeration | ||||
| F.5 Type of submission | enumeration | ||||
| F.6 Other token characteristics | textBlock | - UTXO-based transaction model with Ed25519 digital signatures - Proof of Work consensus using SHA-256 double hash - 15-second target block time with adaptive difficulty (range 1-7, +/-1 per block) - 8 decimal places (smallest unit: 0.00000001 FTC) - Total supply cap: 1,000,000,000 FTC - Emission: Exponential decay from 50 FTC/block, asymptotically approaching total supply - Transaction fees: 0.1% of amount (min 0.00002 FTC, max 0.1 FTC) - Mandatory compliance gateway enforced at protocol level above block 360,000; gateway signatures use a hybrid Ed25519 + FALCON-512 (post-quantum) scheme - Pre-transaction compliance screening via Heimdall engine (22 chapters, 131 control codes) - Native ISO 20022 PACS.008.001.13 support with two-tier storage |
|||
| F.7 Commercial name or trading name | text | ||||
| F.8 Website of the issuer | text | ||||
| F.9 Starting date of offer to the public or admission to trading | date | ||||
| F.10 Publication date | date | ||||
| F.11 Any other services provided by the issuer | textBlock | ||||
| F.12 Language or languages of white paper | text | ||||
| F.13 Digital token identifier code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available | text | ||||
| F.14 Functionally fungible group digital token identifier, where available | text | ||||
| F.15 Voluntary data flag | boolean | ||||
| F.16 Personal data flag | boolean | ||||
| F.17 LEI eligibility | boolean | ||||
| F.18 Home member state | enumeration | ||||
| F.19 Host member states #1 | enumerationSet | ||||
| F.19 Host member states #2 | enumerationSet | ||||
| F.19 Host member states #3 | enumerationSet | ||||
| F.19 Host member states #4 | enumerationSet | ||||
| F.19 Host member states #5 | enumerationSet | ||||
| F.19 Host member states #6 | enumerationSet | ||||
| F.19 Host member states #7 | enumerationSet | ||||
| F.19 Host member states #8 | enumerationSet | ||||
| F.19 Host member states #9 | enumerationSet | ||||
| F.19 Host member states #10 | enumerationSet | ||||
| F.19 Host member states #11 | enumerationSet | ||||
| F.19 Host member states #12 | enumerationSet | ||||
| F.19 Host member states #13 | enumerationSet | ||||
| F.19 Host member states #14 | enumerationSet | ||||
| F.19 Host member states #15 | enumerationSet | ||||
| F.19 Host member states #16 | enumerationSet | ||||
| F.19 Host member states #17 | enumerationSet | ||||
| F.19 Host member states #18 | enumerationSet | ||||
| F.19 Host member states #19 | enumerationSet | ||||
| F.19 Host member states #20 | enumerationSet | ||||
| F.19 Host member states #21 | enumerationSet | ||||
| F.19 Host member states #22 | enumerationSet | ||||
| F.19 Host member states #23 | enumerationSet | ||||
| F.19 Host member states #24 | enumerationSet | ||||
| F.19 Host member states #25 | enumerationSet | ||||
| F.19 Host member states #26 | enumerationSet | ||||
| F.19 Host member states #27 | enumerationSet | ||||
| F.19 Host member states #28 | enumerationSet | ||||
| F.19 Host member states #29 | enumerationSet | ||||
| Part G - Information on rights and obligations attached to other tokens | |||||
| G.1 Purchaser rights and obligations | textBlock | 1. Transaction Fee Payment: FTC is used to pay transaction fees on the FutureChain network. 2. Network Participation: FTC holders may participate in mining and transaction validation. 3. Service Access: FTC enables access to FutureChain compliance and ISO 20022 services. Obligations of FTC holders: 1. Key Security: Securing private keys; lost keys cannot be recovered. 2. Regulatory Compliance: Complying with applicable laws in their jurisdiction. 3. Tax Reporting: Reporting and paying any applicable taxes. 4. Transaction Verification: Verifying transaction details before signing. 5. Software Updates: Maintaining compatible wallet software. FTC does NOT confer: ownership in FutureChain AB, voting rights, dividend entitlement, redemption rights, guaranteed value, interest or yield, or collateral backing. |
|||
| G.2 Exercise of rights and obligations | textBlock | ||||
| G.3 Conditions for modifications of rights and obligations | textBlock | ||||
| G.4 Future public offers | textBlock | ||||
| G.5 Issuer retained other token | integer | ||||
| G.6 Utility token classification | boolean | ||||
| G.7 Key features of goods or services utility tokens | text | ||||
| G.8 Utility tokens redemption | text | ||||
| G.9 Non-trading request | boolean | ||||
| G.10 Other tokens purchase or sale modalities | text | ||||
| G.11 Other tokens transfer restrictions | text | ||||
| G.12 Supply adjustment protocols | boolean | ||||
| G.13 Supply adjustment mechanisms | text | ||||
| Other token schemes details | |||||
| G.14 Token value protection schemes | boolean | ||||
| G.15 Token value protection schemes description | textBlock | ||||
| G.16 Compensation schemes | boolean | ||||
| G.17 Compensation schemes description | textBlock | ||||
| G.18 Applicable law | textBlock | ||||
| G.19 Competent court | textBlock | ||||
| Part H – Information on underlying technology | |||||
| H.1 Distributed ledger technology (DTL) | text | ||||
| H.2 Protocols and technical standards | text | ||||
| H.3 Technology used | textBlock | - Language: Rust 2021 (memory safety, performance) - Runtime: Tokio (high-performance async I/O) - Storage: RocksDB (proven key-value store) - Networking: rustls + TLS 1.3 (enforced on all P2P communications) - Cryptography: Ed25519 (transaction signing), hybrid Ed25519 + FALCON-512 (NIST FIPS 206 FN-DSA, post-quantum) for compliance-gateway signatures, AES-256-GCM (data encryption), Argon2id / PBKDF2 (key derivation), SHA-256 (block hashing) - Compliance signer registry: 30 signers, HSM-backed via SoftHSM2 / PKCS#11 - HSM: PKCS#11 support (SoftHSM2 verified, compatible with Thales Luna, AWS CloudHSM, Azure Key Vault) - ISO 20022: Native PACS.008.001.13 with two-tier storage (on-chain hash + encrypted off-chain full message) - Node types: Standard (mining), Full (90-day ISO store), Archive (unlimited ISO store) - Public RPC: Bahnhof endpoint (https://rpc.futurechain.eu) behind a Caddy reverse proxy with Let's Encrypt TLS, bearer authentication, rate limiting, and signed-challenge enrollment |
|||
| H.4 Consensus mechanism | text | ||||
| H.5 Incentive mechanisms and applicable fees | text | ||||
| H.6 Use of distributed ledger technology | boolean | ||||
| H.7 DLT functionality description | textBlock | 1. Consensus: Proof of Work with SHA-256, providing permissionless network security 2. Two-Tier Storage: On-chain blockchain (~800 bytes/tx) + off-chain encrypted ISO 20022 store (5-15 KB/tx), achieving 99.5% on-chain storage reduction 3. Pre-mempool Compliance: A mandatory compliance gateway (enforced above block 360,000) screens transactions before blockchain admission; country-jurisdiction and sanctioned-wallet-address screening are actively enforced, with the remaining Heimdall controls in shadow mode under a graduation policy 4. P2P Network: Gossip protocol with mandatory TLS 1.3 encryption on all node communications 5. Cryptographic Compliance Proofs: Every approved transaction carries a compliance-node signature under a hybrid Ed25519 + FALCON-512 (post-quantum) scheme, creating immutable, quantum-safe audit evidence (legacy secp256k1 signatures from the pre-migration window remain verifiable for historical transactions) 6. GDPR Compatibility: Off-chain personal data can be deleted while on-chain hashes (non-personal data) remain immutable 7. Public RPC Access: A hardened public endpoint (https://rpc.futurechain.eu) lets partners and wallet applications interact with the chain without running a full node |
|||
| Other token audit details | |||||
| H.8 Audit | boolean | ||||
| H.9 Audit outcome | textBlock | ||||
| Part I - Information on risks | |||||
| I.1 Offer-related risks | textBlock | - Price Volatility: FTC value may fluctuate significantly due to market conditions, speculation, or regulatory changes. Total loss of investment value is possible. - Limited Liquidity: FTC may not be listed on exchanges or may have limited trading volume, preventing sale at desired price or timing. - No Intrinsic Value: FTC has no underlying assets, revenue stream, or guaranteed utility. Value depends entirely on market demand. - Market Manipulation: Crypto markets may be subject to manipulation, wash trading, or coordinated activity. |
|||
| I.2 Issuer-related risks | textBlock | - Project Failure: FutureChain AB may fail to achieve its objectives or cease operations, resulting in reduced or no FTC utility. - Team Departure: Key personnel may leave the project, causing development slowdown or failure. - Funding Shortage: Insufficient funding may limit development, leading to incomplete or abandoned features. - Adoption Failure: Financial institutions may not adopt FutureChain technology, resulting in limited network utility. - Newly Established: FutureChain AB is a newly established company with no operating history or revenue. |
|||
| I.3 Other tokens-related risks | textBlock | - No Guaranteed Value: FTC has no price peg, no reserves, and no value protection mechanism. - Not Covered by Compensation Schemes: FTC is not covered by any deposit guarantee, investor compensation, or similar scheme. - Irreversible Transactions: Blockchain transactions cannot be reversed once confirmed. Lost private keys cannot be recovered. - Key Loss: Private keys, if lost or stolen, result in permanent loss of all associated FTC. - Cryptographic Advances: Advances in cryptography (e.g., quantum computing) may weaken current security in the long term. |
|||
| I.4 Project implementation-related risks | textBlock | - Competition: Competitors may develop superior technology, reducing FTC adoption and value. - Third-Party Dependencies: Reliance on external services (Heimdall compliance data providers) introduces operational dependencies. - Regulatory Changes: Future regulatory developments may restrict or prohibit FTC or impose additional compliance burdens. - Classification Changes: Regulators may reclassify FTC (e.g., as a security), imposing additional requirements. - Technology Evolution: Rapid changes in blockchain technology may render current architecture less competitive. |
|||
| I.5 Technology-related risks | textBlock | - Software Bugs: The FutureChain codebase (75,000+ lines of Rust) may contain undiscovered bugs or vulnerabilities, potentially causing loss of funds or network disruption. - Security Breaches: Despite multi-layer security measures, the network may be compromised by sophisticated attackers. - Consensus Attacks: 51% attacks or other consensus-level attacks may enable transaction reversals or double-spending. - Network Partition: Software incompatibilities may cause network splits, creating confusion and value dilution. - Mining Centralization: Mining power may concentrate in few hands, creating censorship or manipulation risks. - Scaling Limitations: The network may not scale to meet demand, causing congestion and high fees. |
|||
| I.6 Mitigation measures | textBlock | - Security: 7-layer defense architecture, mandatory TLS 1.3, HSM support, AES-256-GCM encryption, comprehensive audit logging - Compliance: Pre-transaction Heimdall screening across 22 areas and 131 control gates; country-jurisdiction and sanctioned-wallet-address screening are actively enforced, with the remaining controls in shadow mode under a documented graduation policy - Transparency: Open documentation, planned external security audit, regulatory engagement with Finansinspektionen - Development: Memory-safe Rust implementation, comprehensive test suite, continuous monitoring via Prometheus/Grafana/Loki stack - Patent Protection: Pending patent application with Swedish PRV covering core innovations |
|||
| Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts | |||||
| J.1 Adverse impacts on climate and other environment-related adverse impacts | textBlock | ||||
| Mandatory information on principal adverse impacts on the climate and other environment-related adverse impacts of the consensus mechanism | |||||
| General information about adverse impacts | |||||
| S.1 Name | text | ||||
| S.2 Relevant legal entity identifier | text | ||||
| S.3 Name of the crypto-asset | text | ||||
| S.4 Consensus mechanism | text | ||||
| S.5 Incentive mechanisms and applicable fees | text | ||||
| S.6 Beginning of period to which disclosed information relates | date | ||||
| S.7 End of period to which disclosed information relates | date | ||||
| Mandatory key indicator | |||||
| S.8 Energy consumption | energy (kWh) | ||||
| Sources and methodologies | |||||
| S.9 Energy consumption sources and methodologies | textBlock | ||||
| Supplementary information on principal adverse impacts on climate and other environment-related adverse impacts of consensus mechanism | |||||
| Supplementary key indicators | |||||
| S.10 Renewable energy consumption | percent | ||||
| S.11 Energy intensity | energy (kWh) | ||||
| S.12 Scope 1 DLT GHG emissions - controlled | GHG emissions (tCO2e) | ||||
| S.13 Scope 2 DLT GHG emissions - purchased | GHG emissions (tCO2e) | ||||
| S.14 GHG intensity | GHG emissions (tCO2e) | ||||
| Sources and methodologies | |||||
| S.15 Key energy sources and methodologies | textBlock | ||||
| S.16 Key GHG sources and methodologies | textBlock | ||||
| Optional information on principal adverse impacts on the climate and on other environment-related adverse impacts of the consensus mechanism | |||||
| Optional indicators | |||||
| S. 17 Energy mix | percent | ||||
| S.18 Energy use reduction | |||||
| Energy use reduction target (absolute value) | energy (kWh) | ||||
| Energy use reduction target (percentage) | percent | ||||
| S.19 Carbon intensity (kgCO2e/kWh) | decimal | ||||
| S.20 Scope 3 DLT GHG emissions - value chain | GHG emissions (tCO2e) | ||||
| S.21 GHG emissions reduction targets or commitments | textBlock | ||||
| S.22 Generation of waste electrical and electronic equipment (WEEE) | mass (tonnes) | ||||
| S.23 Non-recycled WEEE ratio | percent | ||||
| S.24 Generation of hazardous waste | mass (tonnes) | ||||
| S.25 Generation of waste (all types) | mass (tonnes) | ||||
| S.26 Non-recycled waste ratio (all types) | percent | ||||
| S.27 Waste intensity (all types) | mass (tonnes) | ||||
| S.28 Waste reduction targets or commitments (all types) | textBlock | ||||
| S.29 Impact of use of equipment on natural resources | textBlock | ||||
| S.30 Natural resources use reduction targets or commitments | textBlock | ||||
| S.31 Water use | volume (m3) | ||||
| S.32 Non recycled water ratio | percent | ||||
| Sources and methodologies | |||||
| S.33 Other energy sources and methodologies | textBlock | ||||
| S.34 Other GHG sources and methodologies | textBlock | ||||
| S.35 Waste sources and methodologies | textBlock | ||||
| S.36 Natural resources sources and methodologies | textBlock | ||||