|
1
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: April 07, 2021, 07:56:39 PM
|
That’s the spirit, Joe_Bauers_👻! No pain! NO PAIN! (Well—maybe a little a lot of pain.) I infer that this must be your experience as a Yacoiner: Perhaps this may comfort you: Yacoin has inspired me! As an expert in pessimization, I want to create a coin that is even worse: Slower, more wasteful of resources, and not merely impractical, but humanly impossible to use. I have some great ideas for this. If you want to be a bagholder for a coin even worse than Yacoin, then I will be happy to prey on your financial masochism! Seriously, I am assembling a team of world-class pessimization experts for this. 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. |
|
|
|
|
3
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: April 03, 2021, 08:56:33 PM
|
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 Jesus... GET A LIFE. You won't go away will you. Worthless!
It's called consensus buddy. I suggest you learn what that means? No one cares what you think. NO ONE.
Want to post that private message?
Sure. Windmaster... WHERE ARE YOU??
Who is Windmaster to you exactly? Your daddy?
Last active over 3 years ago... It all makes sense now. lol
I hate to break this to you about your daddy... but.. but.. he had a large GPU mining operation back in 2013. It was impressive, especially at the time. I imagine he has brought that back to some degree if he is still around somewhere. I would welcome your daddy to mine and support YACoin 1.0!
Good luck on your YACoin Cash project you miserable clown!
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. |
|
|
|
|
4
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: March 30, 2021, 06:23:26 PM
|
Beave162 quack quack quack
[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. if (
(0 < nPosBlockCount)
&&
(
(
fTestNet
&&
pprev
)
||
!fUseOld044Rules //(nTime >= YACOIN_NEW_LOGIC_SWITCH_TIME)
)
) 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 you're 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 I chose to amuse myself as in this case it's better than the original) 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. |
|
|
|
|
5
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: March 30, 2021, 01:02:45 AM
|
God, you are an absolute, pathetic loser.
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  |
|
|
|
|
6
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: March 29, 2021, 06:46:24 PM
|
I'm wondering how it was decided to convert YAC to POW only. I don't recall seeing a discussion here, in GitHub, or miners voting with their hashrate. YACoin Resurrection Hard Fork – Heliopolis
Agree. I was mining yac since the beginning. This is pretty decent currency, why spoil it? v1.0 client is unstable, crashes all the time. I propose staying at the old one for a longer time. No hard fork is needed. Why? 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. 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. It's interesting to me that Pakapaka used the correct hashing for testnet... static const uint256 hashGenesisBlockTestNet("0xfe20c2c2fc02b36d2473e1f51dba1fb455d41ff42966e2a4edabb98fdd7107e6"); if only they would have switched that around! 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. |
|
|
|
|
7
|
Bitcoin / Development & Technical Discussion / Re: PSA: Coders making ad hoc “random” schemes are like kids playing with matches.
|
on: March 27, 2021, 07:20:28 PM
|
@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 miner could "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. unsigned char CBlockHeader::GetNfactor() const
{
std::string spb = hashPrevBlock.ToString();
std::string lasthashchar = spb.substr(block_length,1);
unsigned char Nfactor = 20;
if((spb == "0000000000000000000000000000000000000000000000000000000000000000")){
Nfactor = 4;} // Genesis, all chains.
else if((lasthashchar == "0") || (lasthashchar == "1") || (lasthashchar == "2") || (lasthashchar == "3")){
Nfactor = 18;}
else if((lasthashchar == "4") || (lasthashchar == "5") || (lasthashchar == "6") || (lasthashchar == "7")){
Nfactor = 19;}
else if((lasthashchar == "8") || (lasthashchar == "9") || (lasthashchar == "a") || (lasthashchar == "b")){
Nfactor = 20;}
else if((lasthashchar == "c") || (lasthashchar == "d") || (lasthashchar == "e") || (lasthashchar == "f")){
Nfactor = 21;}
return Nfactor;
} Since you don't wish further posts on this. Joe_Bauers is asking a question about the mining algorithm for his altcoin, which currently has “Market Cap Rank: N/A” on CoinGecko—but it’s listed on Yobit with a 40% spread (!) and no depth (!!), if you want to get cheated.
His mining algorithm has a flaw he does not see. When time permits, I may post on his altcoin’s development thread with advice for miners who want to exploit it. The discussion is off-topic on this thread; I will delete further posts about it.
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. |
|
|
|
|
9
|
Bitcoin / Bitcoin Discussion / Why do people care who Satoshi is/was?
|
on: March 11, 2021, 08:58:33 PM
|
|
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.
|
|
|
|
|
12
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: February 24, 2021, 02:04:04 AM
|
I'm wondering how it was decided to convert YAC to POW only. I don't recall seeing a discussion here, in GitHub, or miners voting with their hashrate. YACoin Resurrection Hard Fork – Heliopolis
Agree. I was mining yac since the beginning. This is pretty decent currency, why spoil it? v1.0 client is unstable, crashes all the time. I propose staying at the old one for a longer time. No hard fork is needed. Why? 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. |
|
|
|
|
13
|
Bitcoin / Development & Technical Discussion / Re: Will there ever be any monetary incentives to run a full node?
|
on: December 22, 2020, 06:57:51 PM
|
OP has crafted the question thoughtfully:
S/he is not asking whether THERE IS any incentive but if THERE WILL BE such incentive ever. Obviously other than what @gmaxwell has mentioned almost correctly, securing one's own assets there IS no direct financial incentive for running a bitcoin full-node in the current state of the technology either for bitcoin or for any other POW coin. But this fact doesn't prove anything about the potentials of POW cryptocurrencies in general.
That said, one needs to remain focused on the main agenda of bitcoin and its clone: building/developing a decentralized p2p electronic cash, recognizing how critical it is to have the number of active full-nodes as high as possible to serve this sacred cause: decentralization.
So, I formulate the op's question as follows:
Is there any technical solution for a POW based coin to incentivize installing and maintaining active full-nodes preferably without disrupting the whole bitcoin technology?
As a matter of fact, investigating pooling pressure and mining centralization threats in bitcoin I've become convinced that an affirmative approach to the above question is inevitable in the framework of any solid solution to the core problem of mining centralization.
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. |
|
|
|
|
15
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][YAC] YACoin ongoing development
|
on: June 26, 2019, 08:28:00 PM
|
Where is the windows wallet? 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. int CBlockHeader::GetNfactor() const
{
std::string spb = hashPrevBlock.ToString();
std::string lasthashchar = spb.substr(block_length,1);
unsigned char Nfactor = 19;
if((spb == "0000000000000000000000000000000000000000000000000000000000000000")){
Nfactor = 4;} // GENESIS
else if((lasthashchar == "0") || (lasthashchar == "6") || (lasthashchar == "a")){
Nfactor = 22;}
else if((lasthashchar == "1") || (lasthashchar == "b")){
Nfactor = 21;}
else if((lasthashchar == "2") || (lasthashchar == "7") || (lasthashchar == "c")){
Nfactor = 20;}
else if((lasthashchar == "3") || (lasthashchar == "d")){
Nfactor = 19;}
else if((lasthashchar == "4") || (lasthashchar == "9") || (lasthashchar == "e")){
Nfactor = 20;}
else if((lasthashchar == "5") || (lasthashchar == "f")){
Nfactor = 21;}
else if((lasthashchar == "8")){
Nfactor = 22;}
return Nfactor;
}
uint256 CBlockHeader::GetPoWHash() const
{
// uint256 lhash;
uint256 yhash;
// uint256 finalhash;
std::string spb = hashPrevBlock.ToString();
const char *salt(spb.c_str());
size_t salt_len = block_length;
unsigned char rfactor = 0;
unsigned char pfactor = 0;
size_t bytes = 32;
CBlockHeader block_header;
// scrypt_1024_1_1_256(BEGIN(nVersion), BEGIN(lhash));
scrypt_jane(CVOIDBEGIN(nVersion), sizeof(block_header), salt, salt_len, GetNfactor(), rfactor, pfactor, UINTBEGIN(yhash), bytes);
// arith_uint256 ArithLTCHash = UintToArith256(lhash);
// arith_uint256 ArithYACHash = UintToArith256(yhash);
// arith_uint256 CombinedHash = (ArithLTCHash + ArithYACHash);
// finalhash = ArithToUint256(CombinedHash);
// return finalhash; Another potential option scrypt-1024 + scrypt-jane
return yhash;
}
|
|
|
|
|
Show Posts
