bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 5쪽 중 3쪽
ton Coin token provides an optional network-native payment
mechanism for application use. Any application provider can choose to charge
application fees in Canton Coin. For example, the Canton Name Service, an
application offering Validator name lookup and operated by the Super Validators
operating the Global Synchronizer, will charge application fees in Canton Coin.
4. The Canton Coin token provides a public gauge of some aspects of network and
application use. It gives visibility into the fees paid to different application
providers as a proxy of the value that their applications provide to users.
5. The Canton Coin application provides an example of how to build public
applications on the Canton Network.
F.3 Planned Application of
Functionalities
All core functionalities are live.
A description of the characteristics of the crypto-asset, 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 white paper OTHR
F.5 The type of
submission
NEWT
F.6 Crypto-Asset
Characteristics
See 08 above.
F.7 Commercial name or
trading name
N/A
F.8 Website of the issuer N/A
F.9 Starting date of offer
to the public or
admission to trading
Expected around 1 November 2025
F.10 Publication date Expected around 1 October 2025
F.11 Any other services
provided by the issuer
N/A
F.12 Language or
languages of the white
paper
English
F.13 Digital Token Identifier N/A
21 of 35
F.14 Functionally Fungible
Group Digital Token
Identifier
N/A
F.15 Voluntary data flag false
F.16 Personal data flag true
F.17 LEI eligibility N/A
F.18 Home Member State Ireland
F.19 Host Member States Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark,
Estonia, Finland, France, Germany, Greece, Hungary, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia,
Spain, Sweden, Iceland, Liechtenstein and Norway.
Part G - Information on the rights and obligations attached to the crypto-assets
G.1 Purchaser Rights and
Obligations
Rights of Canton Coin Holders:
Canton Coin provides an optional network-native mechanism to pay for network use.
For example, the Super Validators operating the Global Synchronizer allows the
creation of transaction traffic balances across the Global Synchronizer using Canton
Coin.
Canton Coin also provides an optional network-native payment mechanism for
application use. Any application provider can choose to charge application fees in
Canton Coin. For example, the Canton Name Service, an application offering
Validator name lookup and operated by the Super Validators operating the Global
Synchronizer, charges application fees in Canton Coin.
Obligations of Canton Coin Holders:
There are no obligations imposed on Canton Coin holders.
Transferability and Trading:
Holders have the ability to transfer their Canton Coin tokens to others (on-chain) or to
trade them on available markets at will. Ownership of Canton Coin carries with it the
aforementioned access rights, and when a token is transferred, those rights pass to
the new holder. The previous holder loses access once they no longer hold the token.
This means all rights (which are usage rights) are fully transferable with the token.
G.2 Exercise of Rights and
obligations
Holding, transferring or using Canton Coin for payments require no special procedures
beyond having a compatible wallet.
G.3 Conditions for
modifications of rights
and obligations
All actions taken by Super Validators operating the Global Synchronizer, and Canton
Coin application configurations and transactions, are subject to a ⅔ majority action of
all Super Validators. This includes all parameters described in this paper, including the
set of active Super Validators, the minting curve and rights split, fees, and protocol
improvements.
G.4 Future Public Offers N/A
G.5 Issuer Retained
Crypto-Assets
N/A
22 of 35
G.6 Utility Token
Classification
false
G.7 Key Features of
Goods/Services of
Utility Tokens
N/A
G.8 Utility Tokens
Redemption
N/A
G.9 Non-Trading request true
G.10 Crypto-Assets
purchase or sale
modalities
N/A
G.11 Crypto-Assets
Transfer Restrictions
N/A
G.12 Supply Adjustment
Protocols
See H.5 below.
G.13 Supply Adjustment
Mechanisms
See H.5 below.
G.14 Token Value
Protection Schemes
false
G.15 Token Value
Protection Schemes
Description
N/A
G.16 Compensation
Schemes
false
G.17 Compensation
Schemes Description
N/A
G.18 Applicable law Canton Coin is not issued by an identifiable entity and was not sold in any initial coin
offering. Instead, since the launch of the Global Synchronizer, participants operating
nodes connected to the Global Synchronizer have been able to mint Canton Coin
directly from the protocol in exchange for providing either infrastructure or applications
for the Global Synchronizer. These participants are located in jurisdictions across the
world. Thus, there is no single applicable law for Canton Coin.
G.19 Competent court For the reasons stated in G.19, there is no single competent court for Canton Coin.
Part H – information on the underlying technology
H.1 Distributed ledger
technology
Canton Coin is implemented on the Canton blockchain protocol.
H.2 Protocols and
technical standards
Introduction
Several smart contract blockchain networks exist, but they all impose problematic
constraints on assets and applications built on top of them. Specifically, on these
23 of 35
networks, (1) all assets and applications share all data permanently and publicly with
all users, (2) interaction with assets and applications is all-or-nothing; application
operators cannot easily control how different users interact with their applications, (3)
applications compete for global network resources; application operators cannot
independently scale or choose on which infrastructure to deploy. Furthermore, fees
are interconnected and unpredictable, with increased usage in one application raising
costs for all users.
In contrast, most of the world’s assets are heterogeneous, and are governed by
unique rules for how users and businesses transact with them. Operators of
applications that interact with these assets need control over the privacy, scale,
service availability, and infrastructure cost of their applications. As such, the limitations
of existing blockchain networks prevent the onboarding of the bulk of the world’s
assets and processes into an interconnected network, reducing public blockchains’
ability to build substantial network effects outside of crypto-native assets.
For illustration purposes, we contrast existing public blockchain networks with the
most successful public network, the Internet. The Internet is a heterogeneous network
hosting independently operated applications; e.g., Wikipedia is fully public and
coexists with gated banking portals on the same public Internet. High-volume, low-
value services co-exist on the same network as low-volume, high-value services. Each
application provider has the sovereignty to control its application’s unique permissions,
fees, scale, service levels, and more. The Internet has unlimited horizontal scalability
and grows with each application contributed to the network. As a service’s traffic
increases, the application provider adds resources; the growth of one service does not
reduce the resources available to others. The heterogeneity of the applications found
on the Internet helped it reach billions of users. Some users want to go to Wikipedia,
and some want to access their banking portal; both go to the same place - the same
Internet.
The lack of support for application heterogeneity in public blockchains has led to two
significant negative outcomes. First, due to these networks’ privacy limitations, only
assets and data which can be part of the permanent public record are brought into
public blockchains; we see experimentation with cryptocurrencies and non-fungible
tokens (NFTs), but we don’t see enterprises and governments bring traditional assets
and records to public blockchains. Second, to overcome the contention on shared
global resources, the bulk of application logic for blockchain applications is built ‘off-
chain’ under the control of centralized application providers, meaning key functionality
is operated off the shared network, negating the independent verifiability users expect
of public blockchains.
Limitations of existing blockchain networks
Concretely, in Ethereum, and similar smart-contract networks, (1) data is fully
transparent to anyone who can connect to the ledger, (2) there are strict, vertical limits
on transaction capacity on layer 1, (3) layer 2s, rollups, and similar scaling channels
lack transactional composability (4) issuers of assets forfeit control of that asset to a
pool of pseudonymous validators. From a regulatory perspective, the data
transparency and loss of control over assets make these networks unsuitable for use
by financial institutions.
When smart contract applications hit transaction throughput limits, the results are
catastrophic for the network and providers of smart contract applications on the
network. For example, in 2017, Axiom Zen launched the wildly successful application
CryptoKitties on the Ethereum network, exceeding 12% of all network transactions
and causing massive network congestion. As a result, other applications on Ethereum
at this time experienced very high fees and latencies. Following this, the company
behind Axiom Zen built and commercialized a new blockchain, moving away from the
network upon which it built its success, and fragmenting the market.
24 of 35
The scaling limitations of existing blockchains are not inherent to the synchronization
of application data and state; the design of Canton avoids these limitations. Existing
public blockchains force all applications through a single ordering service, even where
this isn’t necessary. But this bottleneck is not required; for example, the order of text
messages in one messaging application should be independent of the order of a
social network feed of another application. These two applications should have
independent ordering mechanisms for their state. Likewise, a network of smart-
contract applications should allow for a similar localization of transaction ordering.
However, ordering across these applications must also be possible, as necessary, to
be an interoperable smart contract network. That requires a shared protocol to
synchronize transactions composed across multiple applications. Current attempts to
allow independent scaling with synchronization across applications, typically known as
layer 2 protocols, rollups, and cross-chain bridges, add significant complexity and
security problems, as evidenced by numerous recent hacks. In contrast, the Canton
Network enables applications across multiple subnets to natively interoperate between
them without requiring a layer 2 protocol or asset bridge.
Canton Network
The Canton Network is a network of networks for smart contract applications with
heterogeneity and scalability properties similar to the Internet, giving application
providers control over their applications.
Like existing blockchain networks, the Canton Network provides real-time
synchronization of sensitive data across participants. It has the privacy of a private
blockchain on a public network; applications on the Canton Network see a single
public ledger. The Canton Network has an expressive smart contract language called
Daml, which has programmable privacy built into every asset or piece of data. The
Canton protocol allows each application to scale independently, increasing availability
and keeping fees low.
Thus, the Canton Network fills a major gap in the public ledger space: it has smart
contracts on a single virtual ledger, similar to Ethereum, Solana, Tezos, and many
more, and it has built-in privacy with selective transparency, similar to the bitcoin
lightning network and Zcash.
Daml
Daml is an open-source smart-contract language and framework designed to make it
easy to develop, operate, and maintain multi-party applications in a way that
preserves privacy and data consistency. More concretely:
1. Daml provides concepts to capture rules that govern real-world business
transactions. This helps programmers focus on business logic only while
avoiding common security pitfalls.
2. Daml allows to specify access and authorization policies within the smart
contract code, making it easy to keep them in sync. Data is confidential by
default, and access policies are easily defined so that the smart contract
programmer can understand and maintain them effortlessly.
3. Daml supports application interoperability by enabling the composition of
workflows into more complex ones, including when the workflows are
already deployed across different applications on different networks. A
party can unilaterally extend functionality by composing existing workflows
into more complex ones. This ability for any party to extend functionality
fosters organic growth of ledger usage and helps manage complexity.
Daml enables the composition of workflows across a network of
applications while maintaining the confidentiality and authorization
requirements of each application.
4. Daml supports interoperability with other systems through integration
25 of 35
tooling, including auto-generation of bindings for common programming
languages, bridges to other blockchains, and common standard and
domain-specific libraries.
Contracts
Daml defines a contract as a codified agreement on a workflow between multiple
parties on the network; these parties are called contract signatories. In addition, other
parties may observe the contract; these are called contract observers. A party can be
an individual entity signing with a private key or a consortium signing with a flexible
multi-signature confirmation policy; as such, assets can be issued, and contracts can
be signed by central parties, or consortiums.
Transactions
A contract is created as part of a transaction, making the contract active. A
subsequent transaction may archive the contract, rendering it archived. To ensure
consistency among network participants while maintaining each contract’s privacy, we
need transactions to exhibit two properties. First, we need a mechanism by which the
different parties agree on the order of transactions to avoid diverging views. Second,
various parties may be entitled to see distinct parts of the transaction based on the
privacy definitions of the specific contracts; we call this sub-transaction privacy.
Transactions must enable parties to have a partial view of the transaction, which they
can verify, also known as a sub-transaction.
The state of active contracts is known as the Active Contract Set (ACS) and is derived
from a transaction graph. Every transaction in the graph may archive and create
contracts, referencing all contracts upon which it depends. New transactions are
atomic changes appended to the end of the transaction graph. The transaction may
consist of multiple sub-transactions, with different parties accessing different sub-
transactions. As such, different parties observe a different subset of the global ACS.
This model is similar to the UTXO transaction model used in bitcoin and other public
blockchains, with two notable differences:
1. No party sees the full transaction graph of the entire network; instead,
each party sees a subset of the graph, also known as that party’s view.
This partitioning of the global transaction graph contrasts to other UTXO
blockchains such as bitcoin and Cardano, in which every party can see
the entire graph.
2. A transaction does not always archive referenced contracts. Whether a
transaction archives an input UTXO or not depends on the application
logic, and is defined in Daml using the keywords consuming and
nonconsuming. This option to keep a referenced contract active is in
contrast to bitcoin and others, in which referencing a UTXO always
archives it.
Transactions are structured as trees; this enables workflows to compose: the trees of
existing workflows become the subtrees of combined workflows. Each party can
validate its subtree and ignore the rest of the transaction.
Said another way, the main difference between Canton’s ledger model and that of
other blockchains is that, in Canton, each party sees only a subset of the ACS and a
subgraph of the global transaction graph, also known as the party’s view. This party-
specific view is always a valid ledger that can be verified locally by the party’s node; a
party need not trust any other party for verification. Upon receiving a transaction or
sub-transaction, a party’s node will verify three things: that the transaction is
consistent with the party’s view, that the transaction conforms with the logic written in
the smart contracts, and that the transaction is properly authorized.
Beyond governing access control, we further utilize this partitioning of the ledger for
parallel processing. Since transactions explicitly declare their dependencies, separate
26 of 35
infrastructures can process independent transactions in parallel; this allows the
Canton Network to scale horizontally by adding capacity as network demand
fluctuates.
This model poses two challenges:
1. We must ensure that different parties’ views of the global ACS are consistent;
in other words, for every contract, the various parties who see it must always
agree on whether it is active or archived.
2. We need an application development model that makes it easy to work with
these restrictive privacy controls. We will show how Daml achieves this.
Smart-contract language
Daml is a modern functional language featuring a static type system that can rule out
many undesired behaviors and correctness errors at compilation time.
Developers define the data schema, workflow semantics, and transaction execution in
contract templates. These are equivalent to object-oriented programming language
class definitions and SQL database schemas. A template defines:
1. Arguments - data the contract stores
2. Choices - actions that parties can take on the contract. Choices are
equivalent to methods in object-oriented programming classes or stored
procedures in databases.
3. Authorization - signatories are parties who must authorize creating or
archiving the contract; observers are other parties who can view the
contract; controllers are parties who can take specific actions on the
contract by exercising contract choices. A party can delegate its
authority to another party to make particular choices. A party that
delegates its authority sees whenever a transaction uses its authority.
4. Constraints - predicates that must hold for every contract of the
template, denoted by the ensure keyword.
Example:
template Iou
with
issuer : Party
owner : Party
currency : Text
amount : Decimal
where
ensure amount > 0.0
signatory issuer, owner
choice Transfer : ContractId Iou
with newOwner : Party
controller owner, newOwner
do
create this with owner = newOwner
By default, exercising a choice archives the contract. In the case of the Transfer
choice above, it also creates a new contract with a new owner. As an improvement on
27 of 35
bitcoin’s UTXO model and Cardano’s eUTXO model, the developer can specify a
choice as nonconsuming. Non-consuming choices do not archive the UTXO, thus
reducing contention.
Daml’s model of explicitly defining authorization enables manual intervention by a
contract’s stakeholders to rectify unexpected situations. Templates make it expl프로젝트로 돌아가기