The first part is basically what Core already does now but only for the last block in every epoch. Rejecting blocks doesn't really solve this problem because then mining turns from "who can find a POW first" to "who can submit a block to the network first after 10 minutes" as the difficulty has become extremely low, and opens up the door to DoS attacks where one group submits all the blocks and selectively drops transactions from addresses they don't like.
And what about waiting 10 min, then share with who got a correct block in the interval? For example store each block found this way: blockfound[second] rewardresult = (reward/number of seconds) // sliced reward for each second blockfound is a list of address that found a block at current diff and deserve a share of the reward foreach second {
numberofblocksfound= size(blockfound[second]);
// if nobody found a block in this second give their reward to the next one
if (numberofblocksfound = empty { rewardresult[second+1]=reward[result[second];}
else {
foreach blockfound {
givereward= rewardresult / numberofblocksfound;
givereward(blockfound,givereward); // create the reward transaction for this address, giving its chunk of the reward.
}
}
}
|
|
|
|
@NotATether thank you for this very interesting answer, I will do some tests. One question bnNew *= params.droughtAdjustmentNumerator;
bnNew /= params.droughtAdjustmentDenominator;
I am not sure about these 2 params. Let say that in that case I want to lower the difficulty by 1.1 (or mult by 0.9) what those 2 values would be? Just take the difficulty percentage or decimal you want to multiply and represent it as a fraction. In this case, to adjust it by 0.9, the numerator is set to 9 and the denominator to 10. This adjustment would happen every time a block is submitted, so it might go down really quickly. So the difficulty will go down quickly until a block is found. Then if a block is found, the difficulty will goes up again x4, which will trigger the adjustment again. This will result in a permanent oscillation, what do you think? Another idea would be to check the time when the new block is found and adjust every block up or down. Or just reject any block that is found < 10 min and start to accept blocks >=10 min with this adjustment to make sure that blocks are found very quickly once the 10 min are reached? What is happening for example when the diff goes down is that blocks are easy again to find, so they are found extremely quickly, which retrigger the diff increase, making difficult to lower the diff and easy to goes up. |
|
|
|
@NotATether thank you for this very interesting answer, I will do some tests. One question bnNew *= params.droughtAdjustmentNumerator;
bnNew /= params.droughtAdjustmentDenominator;
I am not sure about these 2 params. Let say that in that case I want to lower the difficulty by 1.1 (or mult by 0.9) what those 2 values would be? |
|
|
|
|
I am using Basically the same CalculateNextWorkRequired in pow.cpp than Bitcoin in another project.
I only changed the new difficulty target evaluation to move by x2 instead of x4 with Bitcoin.
When my coin was young, difficulty was around 5-10 and we were mining with CPU, that was the cool time.
This algorithm was fine because the steps up and down x2 were not changing the mining requirement that much.
For example we were Diff 5, then it moved to 10, then back to 5, and the blockchain were never stalling because the difficulty was too high.
Now we are at difficulty between 10 Millions and 100 Millions. When the difficulty changes from 10 Millions to 20 Millions, you need to drastically change your hashing power, from 20 TH/s to 50TH/s otherwise, the blockchain stall for hours, or even forever until someone find a block if you are not paying attention.
Are there new algorithms that are more adapted, for example that are changing dynamically the difficulty requirement without finding a new block as soon as the blockchain is stalling more than x minutes?
The current algorithm is not really smart, and require constant re-adjustment for the miners.
Any smart suggestion as a replacement of CalculateNextWorkRequired?
|
|
|
|
I am trying to figure out how https://www.blockchain.com/ calculates the source and destinations of a transaction with the goal to know how much BTC every address owns. I have no problem to get the VOUT getblockhash thehash then for each nTx I get the txhash getrawtransaction txhash which give me the vin and the value of all the transactions. The problem is that I do not have the information as from which address the transactions are coming from. I know the value and the destination, but not the source. In consequence, I can only do the sum of all BTC that were sent to that address, but I cannot subtract the spent BTC. However in https://www.blockchain.com/ they seems to have the source and destination, but for the source, I ignore how they are doing it from the txhash. Anyone could suggest somewhere to look to solve my problem? |
|
|
|
|
It happened that we have been scammed. So we are now focused on other developments.
|
|
|
|
Lot of new things will happen about this project in 2021. Starting by this news. The press release is here: https://kryptofranc.com/franc Franc (FRANC) is a new currency created by the Kryptofranc team. Paris, France 16/01/2021: The authors of Kryptofranc (KYF) a blockchain based on Bitcoin Core are announcing a new project named Franc (FRANC). This new altcoin is a smart contract programmed on the Ethereum (ETH) blockchain with Solidity 8.0. “Franc was the initial project before we decided to do the Kryptofranc” explains Nicolas Choukroun who is the author of the project Franc. Jean Martial Lefranc, who provided the seed financing for the Kryptofranc and I, have moved forward and we have decided to revive the legendary Franc currency as a new Ethereum based token”. “We need a token for our next upcoming exciting project, which will use both Kryptofranc and Franc, and at the same time we are writing history by reviving the Franc, the French currency that was for centuries in the top 5 world’s reserve currency, but was unfortunately fused in the Euro” added Jean Martial Lefranc. For 2 years, ending in 2023, Franc and Kryptofranc will function together in order to offer to the Kryptofranc’s investors a way of stacking KYF to get a 15% APR rewards in Francs. Until then, the only way to get Francs will be to stack Kryptofrancs. Anyone who is holding 5 Million Kryptofrancs or more on a Kryptofranc wallet’s address will receive 0.041% of their holding in the form of Franc tokens every month. Franc will be tradable in a major exchange just as Kryptofranc, and both will empower a still undisclosed project codenamed W.O.K. “Somehow, holders of Kryptofranc (KYF) will be mining Francs (FRANCS) without having the need of any technical skills or any powerful and expensive gears,” said Jean Martial Lefranc, this will reward Kryptofranc’s investors to wait as we rollout the W.O.K project in public beta. Step by step we will reveal the deep purpose of the interaction between Kryptofranc, Franc and W.O.K”! “This is a truly exciting time for me; the ideas started in 2017 are gradually becoming a reality. It is like a puzzle and it will gives a true meaning and a unique practical use of these two Cryptocurrencies. This will help to redefine the realm of crypto by expanding in reach in a more mainstream and playable way for a broad audience. Our investors will have to stick around for the months and years to come and assess the growing value of what we are currently building”, said Nicolas Choukroun. Franc will be traded and functional Q1 2021, stay tuned. You can find Franc website here: https://franc.eu.comThe Kryptofranc website is here: https://kryptofranc.comFollow us at the following social networks: Discord: https://discord.gg/7qscn6SBitcointalk: https://bitcointalk.org/index.php?topic=5157308.0Facebook: https://fb.com/KryptofrancTelegram: https://t.me/kryptofranc |
|
|
|
We are constantly working on improvements. We do not advertise everything. Staking is on our list, we will talk about it soon. we also are working on market making... which is working somehow right now, you can see the bot. We are waiting to have 3 tools: market making, Staking and  (secret right now) These would make keeping the coin more valuable than selling it automatically for the miners. The main problem right now is that many miners are using our SHA256 to mine with Zplan for example which is selling automatically to Bitcoin. KYF is profitable for mining, which explains why we have a very high hash rate. This is driving the price lower, so we are kind of pedaling against the current. We are working on these issues. |
|
|
|
Suggested: // change the hash of BIPs to your genesis hash (see the genesis section) is your genesis hash // do it for main, testnet and regnet. consensus.BIP16Exception = uint256S("0x???"); consensus.BIP34Hash = uint256S("0x???"); => you are doing an altcoin so all the BIP should start at Genesis or very early (see my last answer). So, take the hash from your blockchain and yes it should be the same as the assert.// fix the checkpoint data with your genesis hash, do it for main,testnet and regnet checkpointData = {{{0, uint256S("0x???")},}}; => go in your blockchain and add checkpointData = {{{blocknumber, uint256S("hash")},}}; as checkpoint so that if someone change the the blockchain on purpose, the wallets will reject the change. Do it periodically so that you solidify your blockchain against attackers. Add many checkpoints as your blockchain grows, at block 1000, 10000, 50000, 100000, etc...=========== Suggested: IsNullDummyEnabled has the same problem, do the same to that function. Question: Cant find it?!! Is it in validation.cpp on the latest bitcoin version? => this I do not understand.=========== Suggested: Find this “return state.DoS(100, false, REJECT_INVALID, "bad-cb-height", false, "block height mismatch in coinbase");” and comment it. Question: Cant find it?!! Is it in validation.cpp on the latest bitcoin version? What I do find is this... return state.Invalid(BlockValidationResult::BLOCK_CONSENSUS, "bad-cb-height", "block height mismatch in coinbase"); => the genesis block will shoot this error, so you need to comment it in order to have your wallet to mine, or you will not mine.
Also all similar errors due to SEGWITH security tests needs to be commented, at least for the first blocks. SEGWITH needs to check the block before, and there is none for the first blocks... it is impossible to start mining without commenting these.
then you can reinstall all the BIP tests that were blocking the mining, let say at block 1000 for example and change chainparams.cpp accordingly.=========== |
|
|
|
Suggested: // change the hash of BIPs to your genesis hash (see the genesis section) is your genesis hash // do it for main, testnet and regnet. consensus.BIP16Exception = uint256S("0x???"); consensus.BIP34Hash = uint256S("0x???"); => you are doing an altcoin so all the BIP should start at Genesis or very early (see my last answer). So, take the hash from your blockchain and yes it should be the same as the assert.// fix the checkpoint data with your genesis hash, do it for main,testnet and regnet checkpointData = {{{0, uint256S("0x???")},}}; => go in your blockchain and add checkpointData = {{{blocknumber, uint256S("hash")},}}; as checkpoint so that if someone change the the blockchain on purpose, the wallets will reject the change. Do it periodically so that you solidify your blockchain against attackers.=========== Suggested: IsNullDummyEnabled has the same problem, do the same to that function. Question: Cant find it?!! Is it in validation.cpp on the latest bitcoin version? => this I do not understand.=========== Suggested: Find this “return state.DoS(100, false, REJECT_INVALID, "bad-cb-height", false, "block height mismatch in coinbase");” and comment it. Question: Cant find it?!! Is it in validation.cpp on the latest bitcoin version? What I do find is this... return state.Invalid(BlockValidationResult::BLOCK_CONSENSUS, "bad-cb-height", "block height mismatch in coinbase"); => the genesis block will shoot this error, so you need to comment it in order to have your wallet to mine, or you will not mine.
Also all similar errors due to SEGWITH security tests needs to be commented, at least for the first blocks. SEGWITH needs to check the block before, and there is none for the first blocks... it is impossible to start mining without commenting these.
then you can reinstall all the BIP tests that were blocking the mining, let say at block 1000 for example and change chainparams.cpp accordingly.===========
|
|
|
|
Use this to mine the genesis block static void MineGenesis(CBlockHeader &genesisBlock, const uint256 &powLimit, bool noProduction) {
if (noProduction) genesisBlock.nTime = std::time(nullptr);
genesisBlock.nNonce = std::time(nullptr);
printf("NOTE: Genesis nTime = %u \n", genesisBlock.nTime);
printf("WARN: Genesis nNonce (BLANK!) = %u \n", genesisBlock.nNonce);
arith_uint256 besthash;
memset(&besthash, 0xFF, 32);
arith_uint256 hashTarget = UintToArith256(powLimit);
printf("Target: %s\n", hashTarget.GetHex().c_str());
arith_uint256 newhash = UintToArith256(genesisBlock.GetHash());
while (newhash > hashTarget) {
genesisBlock.nNonce++;
if (genesisBlock.nNonce == 0) {
printf("NONCE WRAPPED, incrementing time\n");
++genesisBlock.nTime;
}
// If nothing found after trying for a while, print status
if ((genesisBlock.nNonce & 0xffff) == 0)
printf("nonce %08X: hash = %s target=%s \r",
genesisBlock.nNonce, newhash.ToString().c_str(),
hashTarget.ToString().c_str());
if (newhash < besthash) {
besthash = newhash;
printf("New best: %s\n", newhash.GetHex().c_str());
}
newhash = UintToArith256(genesisBlock.GetHash());
}
printf("\nGenesis nTime = %u \n", genesisBlock.nTime);
printf("Genesis nNonce = %u \n", genesisBlock.nNonce);
printf("Genesis nBits: %08x\n", genesisBlock.nBits);
printf("Genesis Hash = %s\n", newhash.ToString().c_str());
printf("Genesis Hash Merkle Root = %s\n", genesisBlock.hashMerkleRoot.ToString().c_str());
printf("Genesis Hash Merkle Root = %s\n", genesisBlock.hashMerkleRoot.ToString().c_str());
}
call like this genesis = CreateGenesisBlock(std::time(nullptr), 546521654, 0x1d00ffff, 1, 50 * COIN);
MineGenesis(genesis, consensus.powLimit, true);
Then change the asserts with the merkel and hash generated by this algo. It will work on the latest version of Bitcoin core. |
|
|
|
|
We do not have contacted them yet... We are testing the platform, we still have some developments do be done, like real time evaluation of the total donations, monthly results, and automatic press release generation.
We want to have donated enough to be significant.
Also we would like to have more volume, and be in another exchange.
Then we will contact them.
|
|
|
|
 http://zpool.ca/Hi, We've added KryptoFranc (KYF) to http://zpool.ca/ sha256. See below for connection details. Fee only: 0.5% or less BTC payouts are processed once a day for balances above 0.0025 Payouts for all other currencies are made automatically every 4 hours for balances above 0.05 and balances more than 0.0125 are included in one of the payouts each day. - Sample configurations - To mine and get paid in KYF: -a sha256 -o stratum+tcp://sha256.mine.zpool.ca:3333 -u KYF_ADDRESS -p c=KYF,zap=KYF Exchange to BTC: -a sha256 -o stratum+tcp://sha256.mine.zpool.ca:3333 -u BTC_ADDRESS -p c=BTC Exchange to BTC but mine only KYF: -a sha256 -o stratum+tcp://sha256.mine.zpool.ca:3333 -u BTC_ADDRESS -p c=BTC,zap=KYF All of our ports are NiceHash friendly, no need to specify any extra details We also provide stratum servers in: Europe: sha256.eu.mine.zpool.ca:3333 South East Asia: sha256.sea.mine.zpool.ca:3333 Japan: sha256.jp.mine.zpool.ca:3333 Need hashpower? zpool’s sister provides hash rental services: http://hashtap.ca/============================== Support: https://discord.gg/n45n6Jj Twitter: https://twitter.com/_zpool_ That's a great news, we will post the news on our Discord, Twitter, Telegram etc... tomorrow! Welcome and thanks for your support! |
|
|
|
We have already paid the new exchange, but it took us some time to collect the BTC and send them. This new exchange has been very nice waiting for us.
Now they are taking some time to setup our coin. We have to wait until they are ready. CREX24 took about 1 month to do it.
Patience, patience... it is always stressful to wait (specially after you send some serious money) but, that's the way it is. They waited for us, we are waiting for them.
Great news about the new stock exchange. You probably won't tell the secret yet, which particular stock exchange is it? But tell me at least if it is in the top 20 rankings of coingecko.com https://www.coingecko.com/en/exchanges ?? Today crex24 is 74th. btw, I can see that Asicboost is enabled, http://kryptofranc.cminors-pool.com/, this also indicates progress regards We cannot share any information about the new exchange for 2 reasons. 1- we signed an NDA that specify that nothing can be exposed to the public until it is final. 2- there are some problemes with the law in France and in the state were the new exchange is located that needs to be evaluated, so there is a small but real possibility that listing at this exchange could fail because of a legal issue. We have 2 more mining rig mining KYF, things are moving in the right direction, mining is profitable, we are in the CREX24 faucet since the beginning showing that we are one of the most profitable coin at this exchange. Our volume is small, but that's when it is time to buy right  |
|
|
|
|
We have already paid the new exchange, but it took us some time to collect the BTC and send them. This new exchange has been very nice waiting for us.
Now they are taking some time to setup our coin. We have to wait until they are ready. CREX24 took about 1 month to do it.
Patience, patience... it is always stressful to wait (specially after you send some serious money) but, that's the way it is. They waited for us, we are waiting for them.
|
|
|
|
This new new Block Explorer, this is very good work. Good job.
any news, next development plans this quarter ??
We have paid to be listed in one of the top Exchange in the world (in asia). We are waiting that the integration is finished. That's a pretty big news, since this new exchange is x25 time bigger than CREX24. It is good to see that this platform is moving forward. However, after almost 1 year of launching your project, have you at least assisted 1 NGO during this time? I am seeing only the voting but how long are you gonna collect those votes before you give help to at least 1 NGO? I think it is high time to provide your assistance and not wait long before you lend your help. You can check our voting platform at https://kryptofranc.com we are running a challenge every month. It is just a matter of time until the NGO ask to redeem their KYF (more than 250 NGO in our DB). That's when KYF will really start, when the first NGO will accept KYF payments. |
|
|
|
This new new Block Explorer, this is very good work. Good job.
any news, next development plans this quarter ??
We have paid to be listed in one of the top Exchange in the world (in asia). We are waiting that the integration is finished. That's a pretty big news, since this new exchange is x25 time bigger than CREX24. |
|
|
|
|
Show Posts
