Ludo | Txtx

Results 93 issues of Ludo | Txtx

I've noticed some type discrepancy between this 2 structs: ``` pub struct BurnchainBlockHeader { pub block_height: u64, ... } ``` and ``` pub struct StacksHeaderInfo { ... pub burn_header_height: u32,...

stale

What's our take on updating the API routes and go with something more REST compliant? `/new_mempool_tx` -> `/mempool_tx/new` `/new_block`-> `/block/new` `/new_burn_block` -> -> `/burn_block/new` I was also thinking about maybe...

icebox

With this PR, we are revisiting the integration points between Deno and Clarinet. As explained in https://github.com/hirosystems/clarinet/issues/423, developers have been busy unbundling Deno into smaller crates, which is exciting for...

- support for other addresses types in `btc-payment` deployment ops (`p2wpkh` among others, required for lightning) - ability to receive chainhooks events via `mpsc::channel` - useful when using the `orchestra-event-observer`...

Add aliases to `clarinet run` commands. For instance, ``` clarinet run generate-stacksjs-helper ``` Would run the latest version of that script. That would be more convenient than ``` clarinet run...

functional enhancement

When using commands like `clarinet integrate`, and a file `default.devnet-plan.yaml` is already present, we should probably be recomputing a plan, and comparing it with the one in place, to ensure...

S
deployment-followup
functional enhancement

At some point, clarinet was able to facilitate the fork of contracts, thanks to the command: ``` clarinet contracts fork ``` This command broke a few times in presence of...

deployment-followup
functional enhancement

```typescript Clarinet.test({ name: "Test with pre-setup", deploymentPlan: "./deployments/test-01.yaml", // { chain.mineEmptyBlock(100); }, async fn(chain: Chain, accounts: Map, contracts: Map) { ... ```

deployment-followup
functional enhancement
icebox

deployment-followup
functional enhancement
icebox