Der DHT sharded ab 20 nodes. Schaut gut aus Leute 🤩😁

Die Kaufkraft nit ja auch gut zu😎7sat

https://youtu.be/hgI_L80ZqYE
Steven Venetz
https://youtu.be/hgI_L80ZqYE

Richtig cool den Fortschritt von Junto zu sehen, danke für den Link! :)

https://youtu.be/GwK9rzAzLvE

### Today's update:We are so appreciative of the pre-release testers who have provided great feedback and who've given us the opportunity to begin seeing patterns of 50+ HoloFuel nodes used in a live HoloPort environment.Our plans are to deliver the following releases in this order:1. HoloFuel Enhancements to Pre-Release Testers -- end of this week2. HoloFuel & HP Admin to all Hosts3. HPOS Upgrade (An update to the HoloPort OS to prepare for the hosting release)4. Initial Hosted hApps Release to Pre-Release Testers (Alpha/Beta Testers from Indiegogo will also test this)5. Initial Hosted hApps Release to all Hosts#### The State of Testing & the Upcoming Enhancements ReleaseGenerally testing has been extremely successful. We transacted hundreds of transactions with 56 nodes. Early on we gathered data about new nodes joining the test network. When we began the testing, we thought it was possible that there still might be a few inconsistencies in how data is held between the conductor and sim2h and we believed that might impact how quickly users would sync the DHT data. What we didn’t know was when it might begin to be problematic or how disruptive it might be to the user experience. Towards the end of last week as testers were finishing up the buddy test, a few began experiencing issues. The issues were varied, presenting different symptoms for only a small minority of the nodes. They included challenges with saving one's own HoloFuel nickname, difficulty in syncing such that a recipient nickname failed to resolve, errors displaying in the HoloPort terminal and general delays or an inability to transact. We were able to use the logs of several of the testers who encountered variations of the problem and early this week the Holo Hosting Release team identified the bug that was causing the errors. We believe that all the symptoms experienced were follow-on issue related to the conductor bug. As of yesterday we completed a fix which has now passed dev testing. A few other small enhancements have been made for this version of HoloFuel that allows us to test basic transactions. The upcoming release will include the following:- A fix for the notifications alert to only display for actionable items are in the inbox- A change to include the nickname in the transaction data so as to speed up transaction initiation- A fix for inbox scrolling- A change to side menu navigation display- A consistency fix for decimals on transactions with validation- A footer design fix- A few UI changes to lessen confusion about which buttons to click during transaction creation- New educational messaging to help set expectations on app functions- The Holochain conductor bug fixThere are many, many more features that we are working on for future planned releases into which we will incorporate the test feedback we received. We've asked our pre-release testers to take a short break from testing now so that we can all resume and retest when the upcoming enhancement release is deployed to the test environment. This is expected in the next two days.

Karl
### Today's update:We are so appreciative of the pre-release testers who have provided great feedback and who've given us the opportunity to begin seeing patterns of 50+ HoloFuel nodes used in a live HoloPort environment.Our plans are to deliver the following releases in this order:1. HoloFuel Enhancements to Pre-Release Testers -- end of this week2. HoloFuel & HP Admin to all Hosts3. HPOS Upgrade (An update to the HoloPort OS to prepare for the hosting release)4. Initial Hosted hApps Release to Pre-Release Testers (Alpha/Beta Testers from Indiegogo will also test this)5. Initial Hosted hApps Release to all Hosts#### The State of Testing & the Upcoming Enhancements ReleaseGenerally testing has been extremely successful. We transacted hundreds of transactions with 56 nodes. Early on we gathered data about new nodes joining the test network. When we began the testing, we thought it was possible that there still might be a few inconsistencies in how data is held between the conductor and sim2h and we believed that might impact how quickly users would sync the DHT data. What we didn’t know was when it might begin to be problematic or how disruptive it might be to the user experience. Towards the end of last week as testers were finishing up the buddy test, a few began experiencing issues. The issues were varied, presenting different symptoms for only a small minority of the nodes. They included challenges with saving one's own HoloFuel nickname, difficulty in syncing such that a recipient nickname failed to resolve, errors displaying in the HoloPort terminal and general delays or an inability to transact. We were able to use the logs of several of the testers who encountered variations of the problem and early this week the Holo Hosting Release team identified the bug that was causing the errors. We believe that all the symptoms experienced were follow-on issue related to the conductor bug. As of yesterday we completed a fix which has now passed dev testing. A few other small enhancements have been made for this version of HoloFuel that allows us to test basic transactions. The upcoming release will include the following:- A fix for the notifications alert to only display for actionable items are in the inbox- A change to include the nickname in the transaction data so as to speed up transaction initiation- A fix for inbox scrolling- A change to side menu navigation display- A consistency fix for decimals on transactions with validation- A footer design fix- A few UI changes to lessen confusion about which buttons to click during transaction creation- New educational messaging to help set expectations on app functions- The Holochain conductor bug fixThere are many, many more features that we are working on for future planned releases into which we will incorporate the test feedback we received. We've asked our pre-release testers to take a short break from testing now so that we can all resume and retest when the upcoming enhancement release is deployed to the test environment. This is expected in the next two days.

🥳🥳🥳👌👌