Uncannily accurate!

I've accepted a position at Greenpeace and may not have internet access to check this silly forum for some time, but I would like to contribute the following ideas to your coin if I may.

1) I propose that it is called 0day. Not because of any intentional unknown exploits that you should, of course add to it, but because that's exactly how long anyone will be able to run the client.  <---[cheeze]

2) It should use scrypt-jane like Yacoin, but start at Nf30.

3) Obviously use GetPowHash for generalized hashing, except for validating PoW, which should use MD5. 

"Yacoin Unbroken" sounds like a script that someone should pitch to Stallone for his next movie TBH.

This thread has become useful finally    Tarz, I nominate ~YOU~ to take over the role of YacoinOverlord. Is that OK?

After taking a nice little respite from this silly place, I returned to these PM's

Sure.


Forget Windmaster, I am wondering if Mark Hamill would please join this site and read your PM's for all of us in the voice of Joker.

[MyCousinVinny]
Every thing that guy just said is bullshit[/MyCousinVinny]

Or to put it another way, everything you mentioned is hilariously what you are trying to do. You have the worst mirror complex I've ever witnessed.

As it was already mentioned, where was the vote to convert Yacoin to PoW only made? Oh right, in your garage with your giant custom GPU Yacoin mining rig  

Why is Yacoin still being catered to GPU mining btw? It's supposed to be an ASIC unfriendly CPU coin.

Still, even though I "think" you're an idiot, I'm glad you have a few good programmers helping you.
Here's what you need them to work on, preferably BEFORE you do any hard-fork.

1) Upgrade all code. No one is going to take seriously a coin that is running Bitcoin 0.8.6 code. You mention fixing a few errors, GREAT, what about the few hundred commits that have occurred in Bitcoin since?

2) Stop allowing this nonsense.


What the fuck is that, COBOL?

3) Fix the GetPoWHash issue I mentioned. Litecoin uses GetPoWHash TWICE, Yacoin, almost 100. No serious user or exchange wants to use your bootstrap file to try to offset the 14+ days average of syncing, Bitcoin stopped doing this a long time ago.  Or run a client that uses far more resources than any other, even as a node.

4) Remove the built in miner. You are giving people the impression that they will be able to solo mine blocks against your GPU farm. People need to be incentivized to form Yacoin pools. 

5) Once your done with all that, turn Yacoin over to someone from the community that will keep the coin in the best interest of everyone rather than just their own. Windmaster.... WHERE ARE YOU?

In the meantime, yes I am working on YacoinCash, which uses a new code-base, and fixes all of the above issues with the exception of #3 which as I mentioned before, I am still working on. Of course if Yacoin wasn't being run (into the ground) by an out of touch megalomaniac, maybe we could all work together to fix these issues?

But alas, I guess I will just keep working to fix it all myself.   

This is the PM response from the person I made the terrible mistake of leaving Yacoin to 

I call for a vote of no confidence in the "Leadership" of Beave162.

Stop wasting everyone's time Beave162, or turn Yacoin over to someone that can fix the issues, rather than try to game it so you can mine more blocks with your GPU farm 

Just a quick update, and a clarification.

First, to clarify as it seems there was a lot of confusion by the Yacoin team and perhaps some others, and assumptions here and there seem to overtake the simple act of asking a question    I AM NOT WORKING ON A REPLACEMENT FOR YACOIN I am working on a fork of the original Yacoin protocol, similar to Bitcoin Cash or SPV.

Your Yacoin wallet and coins will be valid until the fork on this chain, and then it will become it's own thing. I encourage anyone that was looking forward to Heliopolis to continue to look forward to it, download, install, what have you. I have changed the network port on the coin I'm working on, so you'll be able to run both on the same machine if you wish.

As far as the update goes, I am likely NOT going to be finished before the Yacoin fork at 1900000. In fact, I may never release it unless I can fix the terrible design flaw that has plagued Yacoin since day one. That is, using the PoW hash for EVERYTHING. This, as you know makes the client use more and more resources to run and gets worse for every Nf change. It shouldn't take a coin 15 days to sync and a  non mining client shouldn't run at a high CPU and Memory rate. That's the main reason Yacoin is not on any exchanges.

There are 2 options I see to fix this.

1) My solution, which I'm not entirely sure is even feasible is to REHASH the Yacoin blockchain. In theory I believe it will work as the underlying data is not changing, just switching the hash field in LevelDB from the ever increasing (in resources) Nf hash with the normal 256 hash. The proof of work will still work, just the hash will be sha256. The client will then be able to sync, from 0 in a few hours.

2) Figure out the best way to transfer all coins to a new block-chain that starts out using the correct 256(256,block) hashing for all but PoW which would still of course use Nfactor. 

This, in my opinion, is the ONLY thing the Yacoin team should be working on. There is one of me and many of you, I'm sure you could devise a solution quicker than I can, but either way (in my opinion) it needs to be done.

I am also happy to have any help from programmers that are extremely familiar with databases, especially LevelDB.

I have nothing to do with Yacoin if that's what you are referring, and it's listed multiple times on the Yacoin thread from the Yacoin lead that Yobit is a scam.

I was asking your opinion on a proof of concept (not production code) to determine the Nfactor from a previous block-hash of a block-chain which seems to have pissed in your Wheaties for some reason  The dreadful result of someone exploiting this obvious flaw you mention is that the Nfactor for the block is going to be 18 instead of, let's say 20. But thanks for your educated and truly useful response.

   

@nullius, I wonder if you would provide your opinion on the following simple algo I devised to determine Nfactor (https://github.com/floodyberry/scrypt-jane) based on previous block hash.

I understand that:
1) This should probably look back to a further level of confirmed block.
2) A vanityaddress could be used to "game the system" by generating a specific char for last position along with the required PoW, though this would require an extra bit of work over non-bad actors.

Apart from that, I would expect a 25% chance overall for each of the 4 options.   

I would buy 100,000 of them. Anyone selling at that price?

Or moving the coins with the password they know right after selling to you.

This seems legit.

How do you know the password is 9 chars? I will trade you 1 LTC for this wallet, with the caveat that I will open it first on my machine and verify.

Why do people care who Satoshi Nakamoto is/was? It's like wondering the name of the person that created the wheel. Sure, I suppose I would be curious about the name of the inventor of the wheel, if nothing else to raise a beer to them from time to time, but ultimately the wheel is the important part of the story.

I didn't read enough into this puzzle to comment... and yet   

Perhaps the equation to be solved is OP's way to provide random numbers? And perhaps it uses the block-chain to do so? Such as this concept for a block-chain generated random N I came up with a few years ago.

Likely for someone to attempt to solve an equation, rather than brute-force it   

Positronic net.

Rather than talk about... in the next 2 weeks, month, etc... blah blah blah... I am going to release something.  I will take a note from Elon Musk who is way better at promotion and say...

Stay Tuned! 

I will say, I'm spending 8+ hours a day working on getting something for the "old" client released ASAP. 

This is NOT to say that I disagree in any way with the current Yacoin team's approach and changes, because I don't in any way. But yes, I agree people should be able to run the old protocol for sure if they wish. 

I actually started working on this a few years ago for a new alt-coin (yes yes, I know) called Poncoin <- Proof of Node. Even came up with a mascot Ponnie the Pinecone lol. Essentially each wallet would have a static (or dynamic) "PON address" that would be hashed with the ip + block to provide key: (ip address + pon address + relayed block = key) That hash would then be added to each relayed block. A certain amount of blocks later, let's say 120, as long as full node was still active, they could redeem a set value. To somewhat alleviate the issue of bad-actors running multiple nodes, a lottery would also be implemented to distribute reward.

There is ABSOLUTELY no reason there shouldn't be a reward for running a full node to answer the initial question, (just ask your local ISP if they think their bandwidth should be free) but I am not as smart as a hair on gmaxwell 's head, so I'm sure there are lots of flaws in my idea. Which is one of the many reasons Poncoin was never done. 

This is somewhat similar to a "Proof of Node" concept I was working on years ago. One thing you might want to consider is forgetting the idea of using IP address and instead adding a "Relayed by" address to each wallet. The longer a node is active, the more reward is given. Also running a full node would add multiplier.

No wallet. You would have to compile. This is a proof of concept for a completely new scrypt-jane PoW only version of Yacoin based on Litecoin code.
Nfactor is randomly selected from previous hash. To work with Yacoin, someone would have to take on the extremely tedious task of including old YAC code and have a date based switch for hard fork.

The other (better) option would be to snapshot Yacoin as of a date and set up a redemption process YAC->NEWCOIN and start this new block-chain from scratch. 

I basically created the new version of Yacoin here but don't have time or interest to continue. Someone should take it from here.
https://github.com/joebauers/litecoin/releases/tag/vrandomnf1.0