Connext BiWeekly Update #6
Demo wallet, bug fixes, wiki.
Published in
2 min readJan 14, 2019
Friends,
It’s been an exciting two weeks since we launched the custodial version of our Hubs and we’ve already made a lot of changes. Without further ado:
💪 Enhancements
- Created a basic demo wallet to showcase Connext functionality. You can find it by navigating to
localhostafter spinning up your Connext hub. Hooray!
🐛 Fixes
- Invalidation states are now properly executed. Previously, the client would incorrectly revert a channel’s state if a contract call failed or if the page was refreshed in the middle of a deposit, leading to unrecoverable state. Turns out, this happened a lot more often than we realized.
- Nondeterministic yarn errors when starting Hub no longer occur largely because yarn was removed entirely.
- A minor vulnerability which allowed a malicious payment sender and hub to collaborate to overwrite thread state for a receiver was found and fixed in the contract.
🔨 Operations
- General docs have been moved to a Github wiki. Repository-specific docs are now correctly available in their repositories as one would expect.
- We’re now doing a better job of tracking issues as they come up in our repositories. We’ve even labeled some good first issues if you want to contribute!
- Our big focus for the next release is to ship the thread pieces to make our architecture noncustodial. More coming soon.
🏁 Loose ends
- If you haven’t already, join our Discord!
- If you’re a meet-up organizer or an enthusiast interested in having a Connext team member speak at your event (or organizing a Connext meet-up), please let us know! We’re always happy to help.
In the meantime, get in touch with us by:
- Joining our Discord
- Tweeting at us
- Emailing us at support@connext.network
- Checking out our website
- Following this medium account
And lastly, please share this with your friends in the community. We’re really excited to help projects in the space scale to the mainstream market!
Thanks for your support,
Team Connext
