HOPR Announcements
Dear node runners,
Exciting news! We're thrilled to announce the release of Dufour version 2.1.0.
What's new?
π‘ Automated strategies:
Efficient node management is crucial for maintaining well-managed payment channels and effectively allocating and collecting funds. With HOPR node strategies, users can perform these tasks seamlessly without needing to manually access the node admin for each action.
π‘ Configuration file:
Our new configuration file gives advanced users granular control over their nodes. This includes configuring strategies, network behavior, RPC providers, chains, inbox settings, and determining which ports and metrics your node exposes.
π‘ Improved UI & UX:
We've made enhancements to the Admin UI, including support for WalletConnect V2 and a new node inbox to cache incoming messages. Numerous small improvements provide more insightful information on your rewards and node status.
For more information on the 2.1.0 release, please visit our https://medium.com/hoprnet/dufour-2-1-0-public-release-4dafff2527f5.
Before upgrading your nodes, please ensure:
- You're using a custom RPC provider. Refer to the docs https://docs.hoprnet.org/node/start-here#understanding-rpc-importance-and-setting-up-your-own-custom-rpc-provider
- Your safe configuration is up to date. Check https://hub.hoprnet.org/staking/dashboard#safe
- Your ISP is providing a public IP.
- If you have a dynamic IP, follow this guide https://docs.hoprnet.org/node/start-here#using-dynamic-dns-ddns
- Upgrade the Admin UI to the latest version: https://docs.hoprnet.org/node/using-hopr-admin-v2
Once you've verified all the above, follow these upgrade steps:
π‘ DappNode users: https://docs.hoprnet.org/node/using-dappnode#update-the-hopr-node
π‘ VPS / Mac / PC users: https://docs.hoprnet.org/node/using-docker#update-the-hopr-node
Thank you for your continued support!
It's time for your tri-weekly DevUpdate π οΈπ‘
Our developers have been working intensively over the past three weeks. Let's check out the updates
π‘ We have closed HOPRd release 2.1.0-rc.4
π‘ We've focused on addressing several bugs in the indexer behaviour, including issues with metrics updates. Notably, we replaced hopr_boost topics with hopr_token in the chain and updated checksum printouts to ensure accurate block id values.
https://github.com/hoprnet/hoprnet/pull/6218
https://github.com/hoprnet/hoprnet/pull/6244
https://github.com/hoprnet/hoprnet/pull/6211
https://github.com/hoprnet/hoprnet/pull/6229
https://github.com/hoprnet/hoprnet/pull/6234
π‘ We also fixed instances where the RPC provider fails, leading to miscalculations in on-chain data checksums. In the event of a failure to load block numbers, the node will robustly restart syncing from the point it left off
https://github.com/hoprnet/hoprnet/pull/6211
https://github.com/hoprnet/hoprnet/pull/6230
π‘ Our pathfinding capabilities have been enhanced to prioritize nodes with proven reliability
https://github.com/hoprnet/hoprnet/pull/6235
π‘ Under the API endpoints, we've implemented restrictions to enforce unique aliases per peer ID. Moreover, we've rectified an issue with empty announced multiaddresses in /node/peers/
https://github.com/hoprnet/hoprnet/pull/6206
https://github.com/hoprnet/hoprnet/pull/6237
π‘ We've addressed subtraction operations on Durations to ensure accurate computations
https://github.com/hoprnet/hoprnet/pull/6233
π‘ To improve connectivity, we've expanded the Peer database connection pool size from 30 to 300
https://github.com/hoprnet/hoprnet/pull/6238
https://github.com/hoprnet/hoprnet/pull/6242
π‘ In addition to bug fixes, we've performed code maintenance by enhancing hopli read identities to display Peer IDs alongside addresses. Furthermore, we've introduced logging of full RPC request and response JSON for improved debugging
https://github.com/hoprnet/hoprnet/pull/6223
As development work begins in earnest on GnosisVPN, we wanted to share some more details about the timeline, and why this is a huge deal for HOPR node runners
First of all: the HOPR token isnβt going anywhere. While itβs likely that GnosisVPN will be a service paid in GNO, xDAO or even fiat (thanks Gnosis Pay!), it will run on top of the HOPR network which is and always will be incentivized in HOPR tokens
The HOPR mixnet is the secret sauce which will make GnosisVPN different from other VPNs. Because every packet takes a different route through the mixnet, thereβs no centralized source which can track and link all your trafficPerhaps even more importantly, websites will see the IP address of the last node in the route, which can i) always be changing and ii) come from any type of IP address, even the Holy Grail of residential IPs. This means that standard geoblocking techniques wonβt work on GnosisVPN
Since geolocation is one of the primary reasons people use VPNs, this be a major selling point for the service
Itβs early days yet: building for generic HTTP relaying is much harder than for RPC calls like we did for RPCh. There are also challenges with balancing throughput and latency, which is why the initial proof of concept will be limited to whitelisted sites in the Gnosis ecosystem like CowSwap
But weβre confident that we can build this, which should mean a lot more organic traffic for the HOPR network and rewards for node runners. As always you follow development on GitHub (https://github.com/hoprnet). Weβre planning to have the prototype ready in late 2024.
HOPRβs proposal at Gnosis DAO to receive $1.5m in investment in exchange for building Gnosis VPN (GIP-98) has passed!
Huge thanks to everyone who participated in the Gnosis forum and voted on Snapshot. This is a major milestone for both HOPR and web3 privacy π₯
You can view the full proposal here: https://forum.gnosis.io/t/gip-98-should-gnosisdao-invest-in-hopr-to-kickstart-development-of-gnosisvpn/8348
What does this mean for HOPR and token holders? First, and most importantly, the HOPR team will receive $1.5m in investment for Gnosis DAO which will greatly extend the development runway.
HOPR node runners will also be eligible to receive 1 GNO to run a Gnosis validator. More details on how to claim and set up your validator will be published soon.
As part of this proposal, HOPR will build a proof of concept VPN called GnosisVPN. This is a natural extension to our work on RPCh, expanding the types of data sent over the HOPR mixnet from RPC calls to more general data transfer protocols. HOPR node runners will be rewarded in $HOPR for relaying GnosisVPN traffic, just like for RPCh and any other service running on top of HOPR.
GnosisVPN will start as a browser extension focused on providing private access to sites and services in the Gnosis ecosystem (e.g., Cowswap, Safe, HOPR staking, etc.). The goal is for this first version to be built by the end of 2024, so weβll be relying on the community for testing and input as we develop, and of course to keep running your nodes to support all the extra traffic this will bring π
For web3 to scale, we need to generate sustainable revenue from real users. This is the cornerstone of the Gnosis 3.0 roadmap, and where better to focus than the $45bn yearly VPN market, which 41% of internet users already participate in. Bringing full-stack privacy while onboarding the masses? Win-win
As always, if you have any questions one of our ambassadors will be happy to answer.
It's time for your tri-weekly DevUpdate π οΈπ‘
Our developers have been hard at work over the past three weeks. Let's dive into the updates
π‘ We have opened HOPRd version 2.1.0-rc.4
π‘ We fixed ticket aggregation between different versions of HOPRd by correcting the incorrect VRF signer
https://github.com/hoprnet/hoprnet/pull/6171
π‘ We fixed an arithmetic overflow issue with time subtractions, which caused the node to crash due to incorrect time arithmetic assumptions
https://github.com/hoprnet/hoprnet/pull/6168
π‘ We also made minor fixes to alias URL decoding, added error codes to certain API endpoints, and deprecated CLI configuration of strategies
https://github.com/hoprnet/hoprnet/pull/6190 https://github.com/hoprnet/hoprnet/pull/6165 https://github.com/hoprnet/hoprnet/pull/6162
π‘ We fixed the issue by updating the node info table with proper upserts, which populate node safe info when a node is pre-registered
https://github.com/hoprnet/hoprnet/pull/6188
π‘ We implemented a workaround for the version matching issue in the Promiscuous strategy
https://github.com/hoprnet/hoprnet/pull/6174
π‘ We enhanced the indexer with a multi-counter metric for contracts seen and a transaction checksum to detect potential missing index logs. Additionally, we fixed the display of sync metric in restarts when no block was produced
https://github.com/hoprnet/hoprnet/pull/6198
https://github.com/hoprnet/hoprnet/pull/6197
https://github.com/hoprnet/hoprnet/pull/6184
https://github.com/hoprnet/hoprnet/pull/6189
π‘ Updated RPC providers to fetch past blocks, waiting until RPC "upsyncs" with the database, and panicking if a chain re-org occurs. Additionally, we added log information when a node gets registered
https://github.com/hoprnet/hoprnet/pull/6193
https://github.com/hoprnet/hoprnet/pull/6166
π‘ Added a PeerID <-> Public key converter to hopli, allowing conversion between PeerID in Base58 and the hex representation of an off-chain public key
https://github.com/hoprnet/hoprnet/pull/6181
πJoin us for an AMA with Gnosis DAO where we will talk about our proposal to Gnosis DAO to build Gnosis VPN - a product on top of the HOPR mixnet
https://forum.gnosis.io/t/gip-98-should-gnosisdao-invest-in-hopr-to-kickstart-development-of-gnosisvpn/8348
Post your questions below, using [AMA] before your question.
πLivestream: https://www.youtube.com/watch?v=tvqQ6X4YmmU
π April 4th
π 6pm CEST
It's time for your tri-weekly DevUpdate π οΈπ‘
Our developers have been hard at work over the past three weeks. Let's dive into the updates
π‘ Main tasks were focused on database optimization and enhancements. We added caching to reduce database call frequency
https://github.com/hoprnet/hoprnet/pull/6132
π‘ Improved chain event processing from the logs and fixed several indexer behavior issues to recognize any on-chain log or event
https://github.com/hoprnet/hoprnet/pull/6129
π‘ Enhanced integration and unit tests and removed unused features and dependencies
https://github.com/hoprnet/hoprnet/pull/6124
π‘ Additionally, we migrated the chain-actions, core-strategy, and chain-indexer crates to the new database
https://github.com/hoprnet/hoprnet/pull/6096
https://github.com/hoprnet/hoprnet/pull/6101
https://github.com/hoprnet/hoprnet/pull/6107
π‘ In terms of API updates, we added a node configuration endpoint, fixed descriptions in API endpoints, added more info to the payload in swagger of messages, and fixed the return code for set alias API call.
https://github.com/hoprnet/hoprnet/pull/6131
https://github.com/hoprnet/hoprnet/pull/6126
https://github.com/hoprnet/hoprnet/pull/6121
https://github.com/hoprnet/hoprnet/pull/6113
π‘ Additionally, we introduced a hopli command to update an identity password
https://github.com/hoprnet/hoprnet/pull/6099
π‘ On the infrastructure side, we fixed commit hash labeling for docker images, updated flake.lock file for nix and migrated hoprd nodes to GCP
https://github.com/hoprnet/hoprnet/pull/6100
https://github.com/hoprnet/hoprnet/pull/6068
https://github.com/hoprnet/hoprnet/pull/6097
It's time for your tri-weekly DevUpdate π οΈπ‘
Our developers have been hard at work over the past three weeks. Let's dive into the updates
π‘ We have migrated HOPRd's data storage from LevelDB to Sqlite as part of which the internal data storage API was able to use ORM. This resolved database locking issues and we improved logging and debugging
https://github.com/hoprnet/hoprnet/pull/6092
https://github.com/hoprnet/hoprnet/pull/6090
https://github.com/hoprnet/hoprnet/pull/6088
π‘ We fixed bugs concerning the auto-redemption for single tickets upon payment channel closure initiation and the use of the exact amount of hops as requested via the API
https://github.com/hoprnet/hoprnet/pull/6084
https://github.com/hoprnet/hoprnet/pull/6079
π‘ We optimized In general HOPRdβs network peer storage for better peer quality calculation and performance
https://github.com/hoprnet/hoprnet/pull/6071
https://github.com/hoprnet/hoprnet/pull/6069
https://github.com/hoprnet/hoprnet/pull/6067
π‘ We added more logging and tracing to help debug code hot-paths, as part of which a bug concerning dual submission of on-chain transactions was fixed
https://github.com/hoprnet/hoprnet/pull/6074
https://github.com/hoprnet/hoprnet/pull/6066
π‘ We have enforced strict configuration file parsing in HOPRd which leads to less runtime issues due to misconfiguration. Moreover general user documentation for the configuration file was improved, errors in unit tests addressed and developer documentation across different crates created
https://github.com/hoprnet/hoprnet/pull/6056
https://github.com/hoprnet/hoprnet/pull/6053
https://github.com/hoprnet/hoprnet/pull/6048
It's time for your tri-weekly DevUpdate π οΈπ‘
π‘ Internal testing of HOPRd v2.1.0-rc.1 began!
π‘ We improved documentation, added configuration file examples, integrated the readme file into the Rust generated documentation.
https://github.com/hoprnet/hoprnet/pull/6006
https://github.com/hoprnet/hoprnet/pull/5955
https://github.com/hoprnet/hoprnet/pull/5938
https://github.com/hoprnet/hoprnet/pull/5936
https://github.com/hoprnet/hoprnet/pull/5902
π‘ We improved the strategy configuration and increasing the aggregation threshold.
https://github.com/hoprnet/hoprnet/pull/5953
https://github.com/hoprnet/hoprnet/pull/5952
π‘ The HOPRd-internal HTTP client switched from async-h1 to isahc
https://github.com/hoprnet/hoprnet/pull/5946
π‘ We fixed docker-compose setup to comply HOPRd 2.1.0, improved metrics, also we allowed checks from the API before indexing.
https://github.com/hoprnet/hoprnet/pull/6002
https://github.com/hoprnet/hoprnet/pull/6007
https://github.com/hoprnet/hoprnet/pull/5942
https://github.com/hoprnet/hoprnet/pull/5957
π‘ We improved the HTTP API
https://github.com/hoprnet/hoprnet/pull/6009
https://github.com/hoprnet/hoprnet/pull/6027
π‘ We updated the Nix environment configuration.
https://github.com/hoprnet/hoprnet/pull/6029
π‘ We improved tests and made lots more bug fixes on v2.1.0
https://github.com/hoprnet/hoprnet/pull/5787
https://github.com/hoprnet/hoprnet/pull/6021
https://github.com/hoprnet/hoprnet/pull/5992
https://github.com/hoprnet/hoprnet/pull/6010
https://github.com/hoprnet/hoprnet/pull/5879
https://github.com/hoprnet/hoprnet/pull/5954
π‘ We fixed duplicate ticket redemption transactions, also we replaced custom finality tracking.
https://github.com/hoprnet/hoprnet/pull/6016
https://github.com/hoprnet/hoprnet/pull/5956
π‘ We added a HOPRd debug image for debugging.
https://github.com/hoprnet/hoprnet/pull/5965
https://github.com/hoprnet/hoprnet/pull/5895
π‘ We created a pipeline to automatically generate the python SDK
https://github.com/hoprnet/hoprnet/pull/5868
Dear node runners!
Exciting news before our upcoming major releaseβversion 2.0.8 is out now! Check out the key changes:
- We've lowered the ticket price from 0.1 to 0.03. Consequently, adjustments have been made to the HOPRd aggregation to optimize your profits: aggregation is triggered when 300 unredeemed tickets are waiting in a channel (instead of 100)
- We fixed the API endpoint, so Dappnode users will now be able to monitor their node's health with Grafana.
Without having 2.0.8 release, you will pay more tx fees for tickets redemption. We recommend to update your nodes!
IMPORTANT: Before upgrading the node, if you were not using a custom RPC provider, please follow these instructions: https://t.me/HOPRannouncements/647
If you were using a custom RPC provider, please follow these steps:
π‘ Dappnode users:
1. Go to Dappstore at http://my.dappnode/installer/dnp.
2. Search for HOPR and click on "Update."
π‘ VPS / Mac / PC users:
1. Execute the command: docker ps. Next to the container image name europe-west3-docker.pkg.dev/hoprassociation/docker-images/hoprd:stable, please write down the container ID.
2. Execute the command: docker rm -f CONTAINER_ID, where CONTAINER_ID is replaced with the one you wrote down.
3. Execute the HOPRd docker command to start the node.
Thank you for your support!
Dear Community,
We're thrilled to share some exciting news with you β our staking hub just got even better with two major features! π₯³
Multisig Feature: Your HOPR Safe now offers enhanced security with the ability to add multiple owners to the same Safe. What does this mean for you? With multiple owners, the risk of wallet vulnerabilities is significantly reduced. Every on-chain action requires approval from the specified owners, ensuring added peace of mind. Learn more about this feature here: https://docs.hoprnet.org/node/using-staking-hub#how-to-setup-multisig
Multiple Nodes Feature: Managing multiple nodes has never been easier! Gone are the days of needing separate addresses for each node. Now, you can conveniently oversee multiple nodes under a single Safe account. Discover more about this feature here: https://docs.hoprnet.org/node/using-staking-hub#how-to-add-multiple-nodes
We want to extend our heartfelt gratitude to each of you for your valuable feedback. Your insights have played a pivotal role in shaping these improvements and making our products even better!
Together, let's continue to innovate and grow as a community. Thank you for being part of this journey with us! π
Warm regards,
HOPR team
Let's see what our devs have been up to these last three weeks π οΈ
π‘ We have launched the most stable HOPRd release, version 2.0.7
π‘ We completed a huge milestone by migrating the HOPR node to Rust! Additionally, we updated dependencies and cleaned up the codebase
https://github.com/hoprnet/hoprnet/pull/5814
https://github.com/hoprnet/hoprnet/pull/5922
https://github.com/hoprnet/hoprnet/pull/5899
https://github.com/hoprnet/hoprnet/pull/5897
https://github.com/hoprnet/hoprnet/pull/5896
https://github.com/hoprnet/hoprnet/pull/5875
https://github.com/hoprnet/hoprnet/pull/5872
https://github.com/hoprnet/hoprnet/pull/5887
π‘ We replaced RustyLevelDB with Sqlite as the primary database backend and made some optimizations
https://github.com/hoprnet/hoprnet/pull/5847
https://github.com/hoprnet/hoprnet/pull/5856
https://github.com/hoprnet/hoprnet/pull/5836
π‘ We implemented websocket support for sending messages
https://github.com/hoprnet/hoprnet/pull/5873
π‘ Under libp2p, we have doubled the number of concurrent connections
https://github.com/hoprnet/hoprnet/pull/5837
π‘ We did small bug fixes in the path selection algorithm, fixed timestamp issues for end-to-end testing, Python SDK, and generating OpenAPI spec
https://github.com/hoprnet/hoprnet/pull/5877
https://github.com/hoprnet/hoprnet/pull/5874
https://github.com/hoprnet/hoprnet/pull/5813
π‘ We also added the utility to generate a default hoprd configuration YAML file and validate any passed-in configuration files
https://github.com/hoprnet/hoprnet/pull/5893
π‘ We improved hoprd-api by adding a timestamp parameter to "peel-all" endpoints and fixed stress tests to run with the refactored hoprd-api
https://github.com/hoprnet/hoprnet/pull/5832
https://github.com/hoprnet/hoprnet/pull/5905
π‘ We have also added nix derivation for hoprd. Additionally, test packages will run the unit tests while the docker packages will build the docker images
https://github.com/hoprnet/hoprnet/pull/5863
https://github.com/hoprnet/hoprnet/pull/5846
Dear node runners,
On January 29th, Cover traffic nodes will stop relaying data through nodes that have not been updated to the latest version 2.0.7. Consequently, those who haven't updated their nodes will not receive tickets, impacting potential rewards.
This measure is aimed at ensuring the health of the HOPR network, with the majority of nodes capable of efficiently relaying data, thereby contributing to a more private and secure network performance.
We appreciate your understanding and tremendous support π
What did you miss in our first full work week of 2024?
π‘ First of all we're happy to see the HOPR network starting strong into the year
https://twitter.com/hoprnet/status/1743573121095868576
π‘ And other people acknowledging our hard work in the privacy space
https://twitter.com/web3privacy/status/1739598419147051192
π‘ If you missed us in Istanbul for DevConnect, you can watch our Safe Staking talk from Multichain Day now
https://twitter.com/RestakingCloud/status/1740031532549714242
π‘ This reads a bit like an obituary but it's still great to see what you can build with Sismo - and we hope that others will pick up this important work!
https://twitter.com/QYuQianchen/status/1740570486600524228
π‘ And finally this is how you can use HOPR today to prevent data harvesting when using your favorite Ethereum wallet
https://twitter.com/RPC_h_/status/1744388735750287674
Dear node runners,
We are delighted to announce that today marks the completion of (hopefully!) the last airdrop distribution for node operators. This signals the resolution of the majority of issues related to tickets aggregation, redemption, and rejected tickets.
βοΈ For nodes still encountering rejected tickets, here are the steps you need to take:
π‘ Dappnode users:
1. Go to: http://my.dappnode/packages/my/hopr.public.dappnode.eth/file-manager
2. Under the "Download file" section, enter: /app/hoprd-db/.hopr-identity and click Download.
3. Unarchive the hopr-identity.tar file, ensuring the view of hidden files is turned on to see the .hopr-identity file.
4. Go to the Config page: http://my.dappnode/packages/my/hopr.public.dappnode.eth/config. Under RPC Provider URL, replace https://provider-proxy.hoprnet.workers.dev/xdai_mainnet with https://rpc.ankr.com/gnosis and click Update.
5. Go to: http://my.dappnode/packages/my/hopr.public.dappnode.eth/info. Next to All containers, click on the Pause icon to stop the HOPRd node.
6. Next to All volumes, click on the trash can to remove all volumes.
7. Restore the identity file:
a) Go to: http://my.dappnode/packages/my/hopr.public.dappnode.eth/file-manager
b) Find the section Upload file and copy the path: /app/hoprd-db
c) Click on Choose file and select your identity file you unarchived before .hopr-identity. Try selecting the file several times until you see the file name instead of Choose file in the field title.
d) Paste the previously copied path into the second field and click Upload.
8. Go to: http://my.dappnode/packages/my/hopr.public.dappnode.eth/info. Next to All containers click on the play icon to start the node.
Wait for up to 1 - 1.5 hours until it syncs with the network!
π‘ VPS / Mac / PC users:
1. Stop the Docker container:
a) Execute the command: docker ps. Next to the container image name europe-west3-docker.pkg.dev/hoprassociation/docker-images/hoprd:stable please write down the container ID.
b) Execute the command: docker rm -f CONTAINER_ID, where CONTAINER_ID is replaced with the one you wrote down.
2. Find the .hoprd-db-dufour folder and delete only the DB folder and the tbf file inside.
3. Next to the latest Docker command (Check the docs page), add the custom RPC provider: --provider https://rpc.ankr.com/gnosis and start a node. You can use any RPC provider you like. More info here: https://t.me/hoprnet/276667
Wait for up to 1 - 1.5 hours until it syncs with the network!
Please update your nodes to the latest version (**2.0.7**) as soon as possibleβοΈFailure to do so will result in the loss of rewards. Only those operating the most recent version will receive rewards seamlessly, avoiding issues such as ticket aggregation, redemption, and rejection problems.
Thank you for your support! π
Dear node runners,
We have recently launched version 2.0.7. Please update your nodes as soon as possible to be able to receive rewards!
Changelog: Mainly, we have prepared a fix for the rejected tickets issue that a few users experienced.
π To update to the latest version, 2.0.7, please follow the steps outlined below:
π‘ Dappnode users
1. Log in to the DAppNode dashboard.
2. Before updating the HOPR package, you need to make a backup. Visit http://my.dappnode/packages/my/hopr.public.dappnode.eth/backup and click on "Backup now". In case this will not workout, please follow this guide: https://t.me/hoprnet/273752
3. Go to the DAppStore, enter HOPR to find the HOPR package.
4. Then click on "Update".
π‘ VPS / Mac / PC users
There are some changes for Docker command users:
- We have increased the memory limit from 2GB to 3GB.
- From now on, you will not need to use tmux or screen apps on your servers. The hoprd Docker container will run in the background, and in case the Docker daemon is restarted, the hoprd container will start automatically.
Guidance on how to update your hoprd nodes:
1. For Docker users, the identity file is automatically created and stored on your OS at the path specified: $HOME/<computer username>/.hoprd-db-dufour/.hopr-id-dufour. Make a backup of this file.
2. If you are using the tmux app, kill all the tmux sessions by using the command: tmux kill-server. If you are using the screen app, kill all the sessions by using the command: killall screen.
3. Please copy a new Docker command from the docs page: https://docs.hoprnet.org/node/using-docker#2-configure-command. Fill in the required fields and start a node!
π¨ We urge you to stay vigilant against potential scammers. The HOPR airdrop will be automatically distributed to all your secure addresses, eliminating the need for any additional actions on your part.
π¨ IMPORTANT: If your node doesn't have the latest version 2.0.7, you are likely losing the rewards you might receive. Please follow the guidance above to upgrade your hoprd node!
HAPPY NEW YEAR π₯
As we enter the new year, let's make a resolution to prioritize our privacy and protect our personal information! Let's be mindful of the data we share & metadata we leak! π‘
Merry Christmas from all of us at HOPR! May your holiday season be filled with love, joy, and privacy π‘
Wishing you a safe and happy holiday season π
Hereβs the last RPCh DepUpdate of 2024! π οΈ
Letβs see what our devs have been up to the past couple of weeks
π‘ We have implemented an optional allowance in the SDK to determine good relay nodes for 1-hop requests and responses, to improve reliability for upcoming 1-hop connections
https://github.com/Rpc-h/RPCh/pull/592
π‘ We have resolved a bug related to receiving the info response from the exit node and bumped the version to V1, reflecting feature stability of the RPCh application
https://github.com/Rpc-h/RPCh/pull/599
π‘ We've made improvements and bug fixes for environment variable handling, aiding in debugging 1-hop messages. Also, we excluded offline exit nodes from 1-hop pairs and enabled logging of failed requests to a file
https://github.com/Rpc-h/RPCh/pull/592
https://github.com/Rpc-h/RPCh/pull/594
π‘ We also made timing improvements. Now, the SDK updates its routes through the network every 11 minutes, facilitating the reselection of available routes. Furthermore, we enhanced the latency of large requests
https://github.com/Rpc-h/RPCh/pull/599
https://github.com/Rpc-h/RPCh/pull/600
Last time this year: what did you miss at HOPR this week?
π‘ We were looking back at the major topics of the year, such as the RPCh Alpha release: https://twitter.com/hoprnet/status/1736053689683505190
π‘ RPCh network stats looking healthy! https://twitter.com/RPC_h_/status/1735646652625477685
π‘ Our Q was giving more insights into payment channels https://twitter.com/QYuQianchen/status/1735460341252038714
π‘ The year is coming to an end but our devs are still busy shipping, e.g. a new hoprd release https://x.com/hoprnet/status/1734966476434473361?s=20
π‘ And finally something forward looking: Epicenterbtc celebrates their 10y anniversary with Sebastian, tune in:
https://twitter.com/hoprnet/status/1735962973963751473
Dear node runners,
The last airdrop has been distributed to all our dedicated node runners! π₯³
We are pleased to inform you that the rejected ticket issue has been successfully resolved! Therefore, we are ending the airdrop. From now on, your node will receive rewards solely from cover traffic.
We urgently request that you update your nodes to version 2.0.6, If you do not upgrade your nodes, you will stop receiving rewardsβΌοΈ
To ensure your node receives rewards, please make sure:
- You have installed the latest version, 2.0.6.
- You have opened a payment channel with at least one random node.
- Your node is visible on https://network.hoprnet.org/dashboard, maintaining at least >80% availability.
π To update to the latest version, 2.0.6, please follow the steps outlined below:
π‘ Dappnode users
1. Log in to the DAppNode dashboard.
2. Before updating the HOPR package, you need to make a backup. Visit http://my.dappnode/packages/my/hopr.public.dappnode.eth/backup and click on "Backup now". In case this will not workout, please follow this guide: https://t.me/hoprnet/273752
3. Get the latest hash from the docs website: https://docs.hoprnet.org/node/using-dappnode
4. Go to the DAppStore, enter hash to find the HOPR package.
5. Then, toggle the βBypass only signed safe restrictionβ on the left, and click on "Updateβ.
π‘ VPS / Mac / PC users
1. For Docker users, the identity file is automatically created and stored on your OS at the path specified: /<computer username>/.hoprd-db-dufour/.hopr-id-dufour. Make a backup of this file.
2. Go to a tmux or screen session, stop the current node by using the CTRL + C keys.
3. Ensure you are using the latest Docker command with the "stable" tag: https://docs.hoprnet.org/node/using-docker#2-configure-command. Fill in the required fields and start a node!
π¨ We urge you to stay vigilant against potential scammers. The HOPR airdrop will be automatically distributed to all your secure addresses, eliminating the need for any additional actions on your part.
Thank you for being a part of the HOPR community!
It's time for your tri-weekly DevUpdate!
Let's see what our devs have been up to these past three weeks
π‘ We have publicly released a stable version 2.0.5 of the hoprd node Dufour
π‘ We made improvements to ticket handling by disabling the redemption of outdated tickets, fixing the off-chain ticket indexer, and calculating the unrealized balance for valid tickets.
https://github.com/hoprnet/hoprnet/pull/5763
https://github.com/hoprnet/hoprnet/pull/5733
https://github.com/hoprnet/hoprnet/pull/5739
π‘ We have stabilized the calculation of network quality
https://github.com/hoprnet/hoprnet/pull/5755
π‘ We migrated the JSON-RPC to Rust. Additionally, we migrated the indexer functionality from TypeScript to Rust and improved the architecture of low-level operations
https://github.com/hoprnet/hoprnet/pull/5675
https://github.com/hoprnet/hoprnet/pull/5716
π‘ We completely removed Tokio runtime and introduced a new HTTP backend client. With this change, you are able the collection of low-level metrics of your hoprd nodeβs RPC usage
https://github.com/hoprnet/hoprnet/pull/5783
π‘ We adjusted the mplex configuration on libp2p to prevent messages from getting dropped when sent all at once
https://github.com/hoprnet/hoprnet/pull/5776
π‘ And finally we fixed the string formatting in HOPR balance
https://github.com/hoprnet/hoprnet/pull/5754
What did you miss last week?
π We rolled out a major update of our hoprd node, many users already upgraded
https://twitter.com/hoprnet/status/1733486663199072760
π Very lovely to see our nodes being used across the world
https://twitter.com/ETHstakingGuide/status/1733281008596975861
π HOPR network and $HOPR protocol revenue keeps growing
https://twitter.com/hoprnet/status/1733154478143250487
π Our @HatsFinance audit competitions is concluded, with fantastic input from the community
https://twitter.com/HatsFinance/status/1732816313028944306
π‘ Alpha leak of developments at @RPC_h_
https://x.com/SCBuergel/status/1733407015542665247
π©βπ« Your weekly nerd education was again proudly presented by our @QYuQianchen
https://twitter.com/QYuQianchen/status/1733104122474213661
β³ We looked at the major events of the year, our Monte Rosa release was a big one
https://x.com/hoprnet/status/1733521879200076062
Dear Node Runners,
The long-awaited HOPRd release, version 2.0.5, is finally here! We've been hard at work, and here's what we've recently accomplished:
1. Automated Ticket Aggregation and Redemption:
- Received tickets will now be automatically aggregated and redeemed. This means that nodes will combine multiple tickets into one, using only a single transaction during the redemption process. This not only streamlines the process but also helps node runners save on gas fees.
2. Resolved Pending Balance Issues:
- We've fixed issues related to pending balances that were preventing the continuous sending of traffic to community nodes.
3. Temporary Disabling of Manual Ticket Redeeming:
- Due to the automation of ticket aggregation and redemption, we have temporarily disabled the manual ticket redeeming function to prevent any potential issues.
While these updates may seem straightforward, the complexity arises from managing multiple components within the network, requiring thorough testing, fixing, and improvement.
Updating to this version is crucial for optimizing your node's performance and ensuring you receive the rewards you deserve.
Node runners, here are the actions you need to take on your end:
π‘ Dappnode users
1. Log in to the DAppNode dashboard.
2. Before updating the HOPR package, you need to make a backup. Visit http://my.dappnode/packages/my/hopr.public.dappnode.eth/backup and click on "Backup now"
3. Go to the DAppStore, search for the HOPR package, and click on "Update"
π‘ VPS / Mac / PC users
1. For Docker users, the identity file is automatically created and stored on your OS at the path specified: /<computer username>/.hoprd-db-dufour/.hopr-id-dufour. Make a backup of this file.
2. Go to a tmux or screen session, stop the current node by using the CTRL + C keys.
3. Ensure you are using the latest Docker command with the "stable" tag: https://docs.hoprnet.org/node/using-docker#2-configure-command. Fill in the required fields and start a node!
π¨ Regarding Cover traffic, to ensure the proper routing of all traffic to community nodes, we are providing a window for node upgrades to the latest version 2.0.5 until December 13th. Subsequently, we plan to discontinue the airdrop and exclusively distribute traffic through cover traffic. Please take the necessary steps to upgrade your nodes by the specified deadline.
What did you miss last week at HOPR & @RPC_h_?
π₯ HOPR got listed on DefiLlama
https://twitter.com/hoprnet/status/1730617762199028059
π€ RPCh keeps showing high levels of reliability for private RPC calls
https://twitter.com/RPC_h_/status/1729531095618617760
πΊ Sebasitanβs talk on why web3 data harvesting is worse than you think is a must-watch
https://twitter.com/SCBuergel/status/1730199192302235688
π¨βπ©βπ§βπ¦ Our first community call with Shutter highlighted the need for encryption and privacy on all layers of the web3 stack
https://twitter.com/project_shutter/status/1729500863930958110
π§ Our QYuQianchen shared another trick of hers for debugging transactions
https://twitter.com/QYuQianchen/status/1730218581986816367
Hereβs a quick RPCh DepUpdate! π οΈ
Letβs see what our devs have been up to the past couple of weeks
π‘ We submitted a Metamask Snap Improvement Proposal to enable RPCh in handling requests
https://github.com/MetaMask/SIPs/pull/119
π‘ We introduced reliable message association and clock-agnostic requests, which will help avoid response failures due to message counter issues, and we fixed compression errors
https://github.com/Rpc-h/RPCh/pull/570
π‘ We have implemented a monthly quota determination that aggregates the quota of subsequent months for users
https://github.com/Rpc-h/RPCh/pull/584
π‘ We fixed a bug which prevents of replay attacks through universally unique identifier tampering
https://github.com/Rpc-h/RPCh/pull/574
What did you miss last week at HOPR?!
π‘ Firstly of course lots of technical developments to improve both RPCh and HOPR
https://twitter.com/hoprnet/status/1726993963045761496
π‘ An interview with @graphprotocol on data science and HOPR's cover traffic
https://twitter.com/graphprotocol/status/1726986630622560425
π‘ The HOPR @DAppNode is on sale!
https://twitter.com/DAppNode/status/1727301103954579503
π‘ Our @QYuQianchen explains how we use @OpenZeppelin at HOPR:
https://twitter.com/QYuQianchen/status/1727649774718042347
π‘ And finally some pretty impressive stats on HOPR nodes, Safes and protocol revenue:
https://twitter.com/hoprnet/status/1728087024832299272
It's time for your tri-weekly DevUpdate!
Let's see what our devs have been up to these past three weeks
π‘ We have migrated the remaining core functionality to Rust and reorganized the package structure to allow a more ergonomic build of the application.
https://github.com/hoprnet/hoprnet/pull/5623
π‘ We performed a Rust migration of RPC API and chain calls.
https://github.com/hoprnet/hoprnet/pull/5538
https://github.com/hoprnet/hoprnet/pull/5719
https://github.com/hoprnet/hoprnet/pull/5709
https://github.com/hoprnet/hoprnet/pull/5707
https://github.com/hoprnet/hoprnet/pull/5724
π‘ We improved database sync and cache management, which enhances data fetching time and cleans up the database in some necessary parts.
https://github.com/hoprnet/hoprnet/pull/5730
https://github.com/hoprnet/hoprnet/pull/5722
https://github.com/hoprnet/hoprnet/pull/5681
https://github.com/hoprnet/hoprnet/pull/5680
π‘ We fixed some minor issues with the aggregated ticket index and resolved a deadlock on ticket rejection.
https://github.com/hoprnet/hoprnet/pull/5693
https://github.com/hoprnet/hoprnet/pull/5692
π‘ We removed the pending balance, which will allow the ticket issuer to issue more tickets than the current channel balance allows.
https://github.com/hoprnet/hoprnet/pull/5690
Here's what happened last week at HOPR & RPCh:
π‘ The week was dominated by EFDevconnect - our @SCBuergel & @rikzrh were busy as never before Istanbul with a total of 4 talks, 4 panels and 2 round table moderations
https://twitter.com/SCBuergel/status/1725794190250905664
https://twitter.com/hoprnet/status/1724684445926457719
π‘ We supported our Gnosischain ecosystem partners Genome (you can still fill out the form to be among the first Genome .GNO domain holders!) https://twitter.com/hoprnet/status/1725151739425247389
π‘ Our Q TLDR-ed the latest Open Zeppelin release:
https://twitter.com/hoprnet/status/1725220787643101485
π‘ And finally our HOPR Core and RPCh product teams are busy building as always, you can follow their progress transparently on GitHub at all times:
https://github.com/hoprnet
https://github.com/rpc-h
What news did you miss from HOPR & @RPC_h_ last week?
π‘ We started with a recap of Rik's privacy talk in Milano earlier this year
https://twitter.com/hoprnet/status/1721864683051765977
π‘ Q shared more insights for Safe nerds & hackers (more alpha coming up on her account)
https://twitter.com/hoprnet/status/1721920444146827566
π‘ If you want to understand the economics of Cover Traffic in depth, check out this explainer video:
https://twitter.com/hoprnet/status/1721920444146827566
π‘ The RPCh team dropped the RPCh server docker container version 0.10.0 with a ton of improvements
https://twitter.com/RPC_h_/status/1722305951896649990
π‘ All numbers up and to the right on the HOPR network
https://twitter.com/hoprnet/status/1723007614622257176
π‘ HOPR is at EFDevconnect in Istanbul right now, many talks, panels & demos coming up, stay tuned!
https://twitter.com/hoprnet/status/1723736338459955612