Skip to main content

100 posts tagged with "hydra"

View All Tags

· One min read
Noon van der Silk

High-level summary​

The team accomplished quite a lot of things, notably the Withdraw Zero trick is now possible, we have documentation for snapshot side-loading, and we have fixed a number of bugs with deposits. We are now focused on our next big release, a Blockfrost-based chain layer, and supporting the Glacier drop.

What did the team achieve?​

  • New metric, hydra_head_peers_connected #1946
  • Withdraw zero trick #1795
  • Better defaults for contestation period and deposit deadline #1925
  • Documentation for the side-loading snapshot feature #1912
  • Bugfixes for deposits #1915, #1895, #1924
  • Head finalised reporting wrong UTxOs #1913
  • Publishing scripts with blockfrost #1668
  • Improved Blockfrost API for following the chain #1931

What's next?​

  • Release version 0.21.0
  • Continued work on a full Blockfrost chain layer #1305
  • Reinstate Kupo support #1785
  • Continue to focus on supporting the Glacier drop
  • Fixes to the documentation #1636,

· One min read
Noon van der Silk

High-level summary​

The team has been working hard on some bugfixes and investigations, as well as a new feature that can be used to "un-stuck" a Hydra head: side-loading snapshots. We're working on some documentation of this feature, and in the coming weeks we will merge several bugfixes, and an implementation of the "Withdraw 0" trick, which will turn out to be very convenient for those wishing to use custom plutus operations on the L2 ledger but still retain the ability to fanout.

What did the team achieve?​

  • New --advertise option to bind to public IPs #1874
  • New feature: Side-loading of a snapshot #1858
  • Mirror node investigation #1859
  • Bugfix for memmory reduction #1917

What's next?​

  • Documentation for the side-loading snapshot feature #1912
  • Tighten security options of the networking layer #1867
  • Publishing scripts with blockfrost #1668
  • Withdraw 0 trick in L2 ledger #1795
  • Various bugfixes #1916, #1924, #1913, #1915
  • More work on Blockfrost and continued support of Hydra users

· One min read
Noon van der Silk

High-level summary​

The team is very excited to have relased the work on reducing the memory footprint of the Hydra node by merging #1618. This has been tested and appears to make a huge impact to long-running Hydra nodes with many transactions. We invite the community to test it more! We also made a couple of hotfixes and documentation improvements.

What did the team achieve?​

  • Merged work on reduced memory footprint for running a Hydra Node #1618
  • Progress on "side-load" of a snapshot #1858
  • Updated documentation for persistence cleaning #1899
  • Fixed a bug where the TUI wasn't getting enough history #1901
  • Allowed for etcd arguments to be passed on #1891; useful for controlling etcd more explicitly.
  • Added /snapshot/last-seen endpoint to query the latest snapshot #1886

What's next?​

  • Finish side-loading snapshots #1858
  • Tighten security options of the networking layer #1867
  • Publishing scripts with blockfrost #1668

· One min read
Noon van der Silk

High-level summary​

The team are very excited to have merged the etcd-based networking stack into master (not yet released). We would appreciate people testing this and reporting any issues! We continue to work on memory usage and potential stuck-head resolutions.

What did the team achieve?​

  • Merged the etcd-based network stack #1720
  • Progress on reduced memory footprint for running a Hydra Node #1618
  • Progress on "side-load" of a snapshot #1858

What's next?​

  • Continue to work on memory usage enhancements #1618
  • Finish side-loading snapshots #1858
  • Tighten security options of the networking layer #1867
  • Publishing scripts with blockfrost #1668

· One min read
Noon van der Silk

High-level summary​

The team is very excited to have the Hydra explorer up-and-running again and now observing over 1,000 heads across all networks and versions! Memory improvements and network resiliance continues to be our focus.

What did the team achieve?​

  • Fixed the hydra-explorer to track multiple vesions of Hydra #1282
  • Made progress on the etcd-based network stack #1720
  • Fixed bug around malformed party information crashing a Head #1856
  • Progress on reduced memory footprint for running a Hydra Node #1618

What's next?​

  • Continue to work on memory usage enhancements #1618
  • Continue working on new networking stack #1720
  • Start work on new approach to "Getting suck" problems; resetting to a previous snapshot #1858