Micah
Micah
This adds the emit keyword (emissions) which is a kind of trace that is used for effectful offchain functionality and therefore should never be erased (even when Silent option to...
If you're building npm/lucid-cardano for vite/sveltekit, there are docs here: https://adastry.io/learn/blog/lucid-svelte-quickstart/ These should be easy to find from the lucid page.
Build transaction, withdraw 0 `"Withdrawal amount doesn't match actual reward balance."` This error shouldn't occur, withdrawing 0 should always be allowed (if script validation passes).
It is unclear whether the project is meant to be licensed (package.json license field) or not so (no license.md). Would there please be a clear indicator? Thank you
Currently I use translucent in browser environment via a messy polyfill. See below: ```ts resolve: { alias: { 'node-fetch': 'node-fetch-polyfill', 'sha256': 'tiny-sha256', '@sinclair/typebox': '@sinclair/typebox', '@dcspark/cardano-multiplatform-lib-nodejs': '@dcspark/cardano-multiplatform-lib-browser', 'uplc-node': 'translucent/uplc/pkg-web', '@emurgo/cardano-message-signing-nodejs': '@emurgo/cardano-message-signing-browser',...
- calculates script data hash correctly - overestimation parameters for the Aiken UPLC evaluator - script hash is only calculated when there's redeemers - protocol params are cached - uplc...
Translucent-blueprint can't be easily used as an NPM command line util because node etc don't natively support typescript so we need to work around that.
Must bring back the blockfrost provider in a way that doesn't make the browser usage of translucent intolerable.
Maestro implementation needs to use amounts-as-strings so that on large value amounts, the json parser doesn't lose precision with JS numbers.