Topic: [ANN] [VIA] ★ Viacoin ★ ~ the future of digital currency ~ ★ - page 54. (Read 825871 times)

I'm sure if early investors knew that VIA was becoming a glorified token to further development work on Bitcoin and Drak's OKCoin account they would have though twice about investing. Saying "well the code will be featured in Viacoin too!" is such a copout. If they wanted to beg for BTC to further develop Bitcoin then be upfront about it, but pitching us a new alt coin that claims to fix the problems of Bitcoin while taking these solutions to Bitcoin is deceptive.

The whole selling point of Viacoin was to do things on its chain that Bitcoin core devs supposedly refuse to implement. Yet suddenly every innovation produced for VIA is actually getting in the Bitcoin code, which makes the original argument for VIA's existence null and void.

Look I know Drak, Todd and you Icebreaker are a bunch of autists who don't think like normal human beings and you think it is perfectly acceptable to ask for almost half a million dollars for a few hundred lines of code but some of us live in the real world where such obscene salaries would normally command in the business world at the minimum a 50-60 hour work week for a whole year and personal cell phone access on the weekends.

This business of Drak getting on twitter everyday, yacking about what is going on in whaleclub, and accusing Gavin of driving people to suicide and then occasionally popping in once a month to write a line or two here and contributing little to the Viacoin github is unacceptable. I'd fired his ass a long time ago if he was on my staff.

The question is has he delivered 600 BTC worth of work and effort into Via? the answer is a solid NO.

What's funny is you got guys like Dave Zimbeck who himself alone built Bithalo, Nighttrader, a working decentralized marketplace with Bitbay, 2-party smart contracts and is in the process of finalizing pegging and all while managing to stay active with his community on an at-least weekly basis and yet he gets called the scammer! 

This whole place really is like high school made up of cliques.

I am not sure I understand the question. CLTV is used in the context of P2SH redeemscripts which means you can create complex scripts with many conditions.
If you can run through what you're trying to do specifically, maybe I'll get a better understand.

CHECKLOCKTIMEVERIFY

REPLACEBYFEE

Here, I'll quote for you, because we all know clicking is hard for millennials.

Btcdrak,

Did you get checktimeverify working with p2sh script signing? I have multisig working but since multisig validates with a template in script.cpp, the new op which adds op_if etc wont validate as there is no template for it, thus im not able to combine signatures using signrawtransaction.

The first leg of a multisig signing works, but doesnt combine othr signatures.

not sure anyone here really cares, but you should.

Peter Todd no longer on the project.   Doesn't look like he contributed much (his own words):

https://www.reddit.com/r/Bitcoin/comments/3s9xtq/peter_todds_role_in_dev/cwvfhqz

not sure anyone here really cares, but you should.

Peter Todd no longer on the project.   Doesn't look like he contributed much (his own words):

https://www.reddit.com/r/Bitcoin/comments/3s9xtq/peter_todds_role_in_dev/cwvfhqz

So.....  600 BTC went where exactly?

It may also be of interest how Viacoin fits into this picture. Firstly, since Viacoin is based on Bitcoin Core it is a downstream project from Bitcoin Core. That means, anything that goes into Bitcoin may also end up in Viacoin. The fact remains that Bitcoin Core is the most active project with the most expertise and peer review in the cryptocurrency ecosystem.

Overall, my goal with Viacoin was to contribute positively to the ecosystem and that even if my project was not successful, that it would have a legacy that was useful for the world at large. The invention of bitcoin is an incredibly important invention for humanity and I want to see the technology develop and succeed.

This being the case, Peter and I agreed that it makes no sense to develop features in a vacuum because this stuff is hard and takes a long time to mature. Even if the target was for Viacoin (and in the example of CLTV, it was first deployed in Viacoin in January 2015), it makes sense that the BIPs and development work go on upstream with the aim of filtering back down. This ensures several criterion are met: that work is well peer reviewed and where possible contributions end up in Bitcoin Core and benefit everyone. If something is included in Bitcoin it must have been considered a good thing and is well peer reviewed and tested. Viacoin will benefit downstream: but the reverse is not true, something developed exclusively for Viacoin will never have the same level of quality.

All things being equal, if the feature/fix is merged to Bitcoin Core, that's a win for the Bitcoin ecosystem and for Viacoin which will get the feature downstream. If the feature is considered a bad idea as revealed by peer review, it stops a bad idea. If the idea is good but too radical for Bitcoin (which is hard to change because of it's size due to risks, or osification), then Viacoin is still at liberty to make the feature itself because Viacoin is much smaller. There almost no ossification and a lot less risks.

Peter is his own man, guided by his own lights. To be clear his principals about Bitcoin override everything. So I let him get on with Bitcoin Core work he wanted but didnt necessarily have time to do without being paid since paid consulting takes priority. I say this because it's not possible to have a conflict of interest with Peter involved, he will never do something he doesn't believe in and want to do in the first place.

I would like to comment about "number of commits". It may not be apparent to readers who are not directly involved in Bitcoin development, but writing code may actually be the least time consuming part of development. The amount of time required to even tests a patch cannot be underestimated. It can take a long time to get things right, and it may take a long time for reviewers to find problems. Unlike most other projects, it is incredible easy to introduce consensus bugs or introduce attack vectors with incredible consequences. Consensus systems really are difficult and code review, testing and security reviews are extremely time consuming. Even when one writes a patch, especially consensus or policy code it is very time consuming to do all the ancillary work of writing BIPs, discussion and championing the pull request and competing for reviewers (yes, literally there is competition to get stuff reviewed because there are so many patches and things going on).

Since all this blocksize debacle, I have also become very involved in Bitcoin Core helping where I can especially in the area of scalability, code review and testing. I can vouch it is entirely possible to spend weeks on end with very little material to show. It's just the nature of the work.

So whether you like or hate Viacoin, CHECKLOCKTIMEVERIFY for example, was materialsed because of it. That is to say, without paying Peter it is very unlikely the necessary work would have done the work on materialising CLTV and it would not have been deployed in Bitcoin today. I take no credit for CLTV, it is an invention of Peter Todd and Greg Maxwell, but I did provide the oil to make it happen. CLTV was deployed (enforced) in Viacoin in January 2015 and we're about to begin deployment in Bitcoin Core. CLTV is widely anticipated by service provider developers (wallets, micropayment channels, lightning network), and I've affectionally nicknamed it OP_HODL. RBF is another big contribution which has seen several iterations. That means a lot of code, and as yet still unmerged, although it seems likely this will be added soon.

Overall, Peter is an incredibly valuable asset to the Bitcoin community. There are very few people with the kind of deep understanding and attention to detail. It has been a privilege working with him.

So Viacoin is waiting to roll out the subsidy reduction hardfork in January (the community reduced the total subsidy to 23MM with halving in January).
There have been regular maintenance releases, another is due shortly.
Next year I'm planning to introduce a new opcode for a type of relative checklocktimeverify being the next piece in the puzzle for retroactive invalidation for more micropayment systems.

Thanks for the follow, I was unable to follow back due to my account being locked (Twitter informed me someone has been trying to compromise my account so I had some difficulties restoring my own access).

Hi Hyperjacked, Thanks! I will contact you this week (via PM)

Of course...my pleasure! Got some cool voice over ideas...

Just write some of your ideas down and PM me...I'm very busy right now but maybe by the end of next week.



Cheers

Cool! Can you make a kind of sexy voice??    You will contact TedUnite?

Hey Goose Babe! I'll do the voice overs...

There have been regular maintenance releases, another is due shortly.
Next year I'm planning to introduce a new opcode for a type of relative checklocktimeverify being the next piece in the puzzle for retroactive invalidation for more micropayment systems.

Just followed you on Twitter...@ohyperjacked

I chatted with otoh on cryptsy today about Viacoin...

What's your plans if any going forward?

cheers

what did otoh have to say?

Just followed you on Twitter...@ohyperjacked

I chatted with otoh on cryptsy today about Viacoin...

What's your plans if any going forward?

cheers

I have made a small presentation on Viacoin:

Edit:
New link: https://twitter.com/tedunite/status/662759486390706176?s=01

We have to raise some awareness with companies and people who are thinking about building an app on top of a blockchain.
who can beat me to make a better one? Shouldn't be too hard  

So ironically we were talking about twitter accounts yesterday and today twitter has locked my twitter account down saying it looks like someone is trying to compromise it and have locked it down. I'm in the process of resolving it, but unable to use the account at the moment.