Use balius to implement smart contracts #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Implement "smart contracts" in the cardano connector. Also remove the dependency on a running cardano node.
Important Changes Introduced
The cardano connector uses a library called balius to build transactions. This library is a runtime for WASM "smart contracts" which run offchain and know how to build cardano transactions. The connector has an API endpoint to "deploy" a smart contract (the endpoint accepts hex-encoded WASM), an endpoint to "invoke" a smart contract, and an endpoint to see the status of an invocation. Notifying firefly-core that the contract has been deployed/invoked has not yet been implemented.
The library is using blockfrost to query against the chain, instead of relying on chainsync from a real cardano node. The demo has also been updated to use an offchain "smart contract" to build its transaction, so you can run the demo end to end while only depending on the blockfrost API.
Future work
Balius itself is still under heavy development, and the API is not yet stable. For this to be production-ready, we'll need to develop it further.
The blockfrost API does not have the right set of endpoints to meet this application's needs without quickly hitting rate limits. We need to enhance blockfrost's APIs and/or work around the rate limits in the paplication.