|
Lmao
Alright let me play along. Where's the github link Dev?
|
|
|
|
Romano, do you intend to do several releases over 2017 with the different roadmap stuff implemented step by step, or will you do only one major release including most (or all) of them? When can we expect a first official release coming from you?  Thank you for all the work you're putting in this coin. I think about several releases. To keep attention from people & making sure atleast most people are running one of my new versions. Especially because even after the roadmap I will just continue the development. |
|
|
|
Commits for today.
I have some more commits staged but it's not entire ready yet, it will be tomorrow or monday.
Working on
indexes: adds additional address, spent and timestamp indexes
The addressindex records all changes to an address for retrieving txids, balances and
unspent outputs for addresses. Changes are stored and sorted in block order. Both p2sh
and p2pkh address types are supported. The index records two sets of key/value pairs.
The first records all activity and is useful for viewing transaction history and
all changes. The second is specifically for retrieving unspent outputs by address, and
is smaller as values are removed once they are spent.
The spentindex has multiple purposes and brings closer together inputs and outputs of
transactions. The main purpose is to efficiently determine the address and amount of
an input's previous output. The second purpose is to be able to determine which
input spent an output.
The timestampindex keeps track of timestamps with block hashes and is useful for searching
blocks by date instead of by height. This is useful for a block explorer that will give
search options by date. The index uses logical time correction to make sure that the
results are sorted in block order. The logical time of a block is actual timestamp of the
block, unless it is less than (earlier) the previous block's logical time, and in that
case it is one second greater than the previous block's logical time.
|
|
|
|
Someone needs to buy you a box of time, for xmas. I wish that would be possible. Time can't be bought  |
|
|
|
More commits. Worked 16 hours on Viacoin today.
|
|
|
|
Pushed extra commits for today.
20/7 busy, ehm I don't want a break but I'm going to take a shower & have dinner.
Will see if i can push extra commits
|
|
|
|
Github commits today.
I might be able to push some extra commits on this friday because the day is not over yet.
I only need 5/6h sleep anyways 
|
|
|
|
Is seg wit really needed? With block times of 1 minute and the same block size as bitcoin shouldn't the transaction velocity be 10x that of bitcoin?
No SegWit's main purpose isn’t a capacity increase. It's for fixing malleability & making scripting easier to upgrade.
It also fixes some long-standing issues, like quadratic hashing.
With third-party and scriptSig malleability fixed, the Lightning Network is less complicated to implement and significantly more efficient in its use of space on the blockchain.
With scriptSig malleability removed, it also becomes possible to run lightweight Lightning clients.
Reduced UTXO growth will benefit miners, businesses, and users who run full nodes
which in turn helps maintain the current security of the Viacoin network as more users enter the system.
Users & developers who help minimise the growth of the UTXO set will benefit from lower fees compared to those who ignore the impact of their transactions on UTXO growth.
Easier changes to script opcodes will make advanced scripting in Viacoin easier.
This includes changes such as introducing Schnorr signatures, key recovery to shrink signature sizes, supporting sidechains & creating even smarter contracts by
using Merklized Abstract Syntax Trees (MAST) and other research-level ideas. |
|
|
|
Great work DEV!
Just wondering if there is a timeline for the roadmap.
SegWit could be done very soon. I know I said within 12 months but more likely it will be done faster. Things are going better than originally planned. |
|
|
|
|
Just builded the binaries.
Need some string re-branding to do in the source code. (Not hard at all, just repetitive work adding "viacoin", "viacoind", "Viacoin" everywhere)
I will continue the string branding tomorrow and tomorrow.
|
|
|
|
hows segwit adding going ?
It's going well. Worked today on it too. Fixed a few things (will do a second post here) I'm now waiting for the wallet to compile & test.
These 2 commits solved it.
Small reminder BIP152 Compact block relay is part of the roadmap
 |
|
|
|
hows segwit adding going ?
It's going well. Worked today on it too. Fixed a few things (will do a second post here) I'm now waiting for the wallet to compile & test. |
|
|
|
Daily update from what I've done today. Some important fixes in the code. Also I saw some problems with the node, fixed that too. Been testing the wallet today, writing down what should be improved. It will get a bit harder tomorrow to push a lot of commits (need some time to think on how to imrove Viacoin.) Anyways looking forward to tomorrow morning to have another productive day  |
|
|
|
Romanornr
Excellent work
Can you post a bitcoin address for me to donate to.
People we need to start showing our true support for this to work. Romanornr clearly is!
I appreciate that. Anyone who donates is really helping me out. My address for funds on Viacoin development: 19Vh7WnR6KuiHhdi3d9oxuz7YbCqKAnzy5 |
|
|
|
|
I would like to inform the community that over the last several weeks I have made contact with several of the the large original ico buyers, or "whales" as most of you guys regard them.
They have been keeping an eye on viacoin's development under my tenure and have been providing advice and guidance.
I hope to address the concerns of all vested parties to build value and make viacoin the currency it was always meant to be.
|
|
|
|
Quoting this because of the new page. |
|
|
|
Wanted to take some rest today but ended up committing more code
I think that's it for tonight. Some more difficult fixes to do but I save those for tomorrow. If I'm lucky, I wake up at 5am to work on Viacoin. Worse case 7am.
Btw... I don't recommend coding this long on a chair. My back starts to hurt to a bit
|
|
|
|
|
Show Posts
