digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-10 00:35:25 +03:00
Code Issues Projects Releases Wiki Activity
40b5eb8476
daml/canton
History
Remy 96f16df3c0
remove script/trigger/cantonFixture deps on scala-bindings (#17954) 
Basically we remove the dependency of different components on "//language-support/scala/bindings" by:

- replacing com.daml.ledger.api.refinements.ApiTypes.Party by com.daml.lf.data.Ref.Party
- replacing com.daml.ledger.api.refinements.ApiTypes.ApplicationId by Option[com.daml.lf.data.Ref.ApplicationId] (here we use option as ApiTypes.ApplicationId allows empty string while Ref.ApplicationId does not).
- adding rounding logic for timestamp in com.daml.lf.data.Time.Timestamp and use it instead of the one from com.daml.api.util.TimestampConversion

Note we did not clean daml-sript export as it have never pass the alpha stage and will be dropped with the 3.x fork.
2023-12-05 15:08:09 +00:00
..
community remove script/trigger/cantonFixture deps on scala-bindings (#17954) 2023-12-05 15:08:09 +00:00
daml-common-staging/daml-errors/src Allow for the construction of shared GlobalKeys. 2023-11-06 20:00:38 +00:00
BUILD.bazel Rewire the build to use ledger-api within canton (#17959) 2023-12-04 16:11:13 +01:00
NO_AUTO_COPYRIGHT update canton to 050547f2 (#17555) 2023-10-12 15:31:11 +02:00
README.md update canton to e5a4cdfc (#17584) 2023-10-17 09:26:56 +02:00
shade_rule Switch from Akka to Pekko (#17814) 2023-11-13 23:22:22 +00:00

README.md

Canton

CircleCI

Canton is a next-generation Daml ledger interoperability protocol that implements Daml's built-in models of authorization and privacy faithfully.

  • By partitioning the global state it solves both the privacy problems and the scaling bottlenecks of platforms such as a single Ethereum instance.

  • It allows developers to balance auditability requirements with the right to forget, making it well-suited for building GDPR-compliant systems.

  • Canton handles authentication and data transport through our so-called synchronization domains.

  • Domains can be deployed at will to address scalability, operational or trust concerns.

  • Domains can be implemented on top of various technologies, depending on the trust requirements.

  • Domains are permissioned but can be federated at no interoperability cost, yielding a virtual global ledger that enables truly global workflow composition.

Refer to the Canton Whitepaper for further details.

Running

Please read Getting Started for instructions on how to get started with Canton.

Consult the Canton User Manual for further references of Canton's configuration, command-line arguments, or its console.

Development

Please read our CONTRIBUTING guidelines.