Transcript of bytemasters Update Portion of the Hangout
Dan Larimer of Cryptonomex speaking with the BitShares community regarding BTS 2.0 updates, STEALTH milestones, Microsoft Azure, Virtual Machines, Ethereum, Mutual Aid Society, Bond Market, the DEX speed and sidechains.
Listen to Episode 138 - Create a BitShares Account
Transcript
fuzzy: Does this put us in a completely different state than most other blockchains that seem to have this centralized crew that is the only one that works on it? Is this kind of like an attempt to move away from that?
bytemaster: Yeah, we like having decentralized development. It protects everyone involved. The regulatory environment is constantly shifting and as companies like Cryptonomex seek investment and growth my open transparency here without the disclaimer this is my personal opinion, can create liabilities for the company.
So I'm just trying to minimize the liabilities that I could place on Cryptonomex by speaking openly with everyone about what I'm thinking and what we're doing. It's purely a CYA [Cover Your Ass] move. So fundamentally I'm still here to offer my feedback on what I know is going on behind the scenes and we'll go from there.
Thom: Seems like it might be a good idea bytemaster if there was something posted in Mumble so people get that disclaimer so that you don't have to state it every time.
bytemaster: Correct. I was stating it at this time so that when fuzzy introduced me in the future he can state it or post it in the text log. Either way it's just here to protect everyone involved. It would be a shame if something happened to me.
That said, we have been very busy behind the scenes addressing a multitude of bugs that and enhancements for BitShares. There will be a new hard fork and it's got several things that are going to be addressed. One fix the serialization bug that prevented us from actually issuing the STEALTH asset like we wanted to. That's done and complete. It will be included in the next hard fork.
We've disabled negative Worker votes, that patches security holes. Fundamentally everyone's got the same amount of influence you just have to be less active in your voting. We've added an option to disable compression on the websocket API. Apparently some browsers are having issues with the repressed stream. But the good news is we've identified the bug that was causing the vast majority of the bandwidth hog for the updates between the server and the wallet. That fix is in there. And it has to do with updating the median feed more often than necessary.
And we're deprecating annual membership. That last one is in progress. abit has two patches, rate limited based transactions and the percentage based transfer fee is in progress. All those changes are going to be rolled out as a single hard fork to minimize the impact to exchanges and other parties. So some of abit's patches are going against the grain of overall Graphene design so they're being reworked and refactored.
Those are the list of things that' we're doing on the back end. On the front end I've identified a handful of issues that have been increasingly annoying to me and I'm sure if they're annoying me they are annoying others. It's part of eating my own dog food. I'm putting pressure on the team to fix the following.
We've increased the timeout on getting the API connection. I don't know how many of you have experienced if your connection is slow or the server is slow you can end up in this infinite loop of hitting retry, getting the connection shortly after and then having to reload and start all over until you can actually do it fast enough. So we're increasing the timeout from 2 seconds to 5 seconds and that should make the wallet load correctly more often even if it is still slow.
We've identified that round trip times to the server between when you click to create a transaction, whether it's to place an order or do a transfer, there's two API calls that go round trip to the server. One to get the updated fees and the other to get the required authorities, which means that it can take several seconds and that makes the user interface feel sluggish if you're using a slow internet connection, a high latency connection or the servers are over loaded. So we're going to prefetch and cache those so that when you click transfer the dialog pops up quickly.
The other thing we're going to be doing is increasing the lifetime of a transaction so it's less likely to expire before getting included in a block. That gives it more time to propagate and gives the user more time to sign if a lot of signatures are required.
The end result of all of these changes should be a dramatic reduction in bandwidth, in cpu time, lower latency, and a more responsive user interface. So those are all of the updates that are going on as far as general enhancements.
Today we're going to be doing another rollout of the STEALTH. That seems to be working better and better. What's new with this rollout is we've got server side backups enabled. So you can actually save your wallet encrypted on the server and recover it. The server will not have the ability to access your private keys. So it will also automatically backup your wallet when things change. This is something that we've been working on for a while and should be coming out testing it in the current release of the testnet UI for STEALTH.
[00:08:08] Server Side Backup Options
[00:09:42] STEALTH UI & Backups
[00:11:44] Liquidity Rewards
[00:20:39] Bond Market Details
[00:24:10] Market Maker & Liquidity
[00:26:21] Sidechains & Regulation
[00:34:22] Mutual Aid Society
[00:35:09] Sidechains
[00:48:21] Virtual Machines, Ethereum & Sidechains
[00:51:09] Tau-Chain & EVM
[00:54:32] Flux Tradeoffs?
[00:56:11] Redundancy Bug Fix & Flux
[00:57:39] EVM & Sidechains
[01:11:00] Microsoft Azure
[01:14:00] Blockstream & Sidechains
[01:15:30] Authority & Sidechains
[01:19:30] Sidechains and Security
[01:22:00] Dan’s Sidechain with Charles Hoskinson
[01:23:20] Hosted Web Wallet