Bitcoin Forum
May 08, 2024, 05:14:15 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: Would you support a new 25% staking reward system?
Yes
No
I'm not staking

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29] 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 »
  Print  
Author Topic: [BITZ] The Only 10% PoS Crypto to have  (Read 81846 times)
drays
Legendary
*
Offline Offline

Activity: 2520
Merit: 1073


View Profile
March 08, 2015, 12:51:24 AM
Last edit: March 08, 2015, 01:03:55 AM by drays
 #561

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

Well, it is not a 100% conclusion, but more of a guess based on few factors:
Here they are:
1. There is no limitation in the function where it is usually set: in GetProofOfWorkReward()
2. Dev (you) did not point to the exact place in the code where the limitation it is set (the only value in main.h equal to 1000000, is MAX_BLOCK_SIZE, which has nothing to do with PoW block limitation as far as I know)
3. No other places found during basic search...

Still, I have no problem accepting you are right and there is a limitation, but please show that, if it is indeed there. I am not FUD'ding, and definitely have nothing against your coin, its just interesting for me as a programmer; though I have extensive c++ background, I am not very familiar with qt-wallet structure Smiley


... this space is not for rent ...
1715145255
Hero Member
*
Offline Offline

Posts: 1715145255

View Profile Personal Message (Offline)

Ignore
1715145255
Reply with quote  #2

1715145255
Report to moderator
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715145255
Hero Member
*
Offline Offline

Posts: 1715145255

View Profile Personal Message (Offline)

Ignore
1715145255
Reply with quote  #2

1715145255
Report to moderator
1715145255
Hero Member
*
Offline Offline

Posts: 1715145255

View Profile Personal Message (Offline)

Ignore
1715145255
Reply with quote  #2

1715145255
Report to moderator
1715145255
Hero Member
*
Offline Offline

Posts: 1715145255

View Profile Personal Message (Offline)

Ignore
1715145255
Reply with quote  #2

1715145255
Report to moderator
EBK1000 (OP)
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000


A Wound in Eternity


View Profile
March 08, 2015, 07:04:25 AM
 #562

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

Well, it is not a 100% conclusion, but more of a guess based on few factors:
Here they are:
1. There is no limitation in the function where it is usually set: in GetProofOfWorkReward()
2. Dev (you) did not point to the exact place in the code where the limitation it is set (the only value in main.h equal to 1000000, is MAX_BLOCK_SIZE, which has nothing to do with PoW block limitation as far as I know)
3. No other places found during basic search...

Still, I have no problem accepting you are right and there is a limitation, but please show that, if it is indeed there. I am not FUD'ding, and definitely have nothing against your coin, its just interesting for me as a programmer; though I have extensive c++ background, I am not very familiar with qt-wallet structure Smiley



It should be static const unsigned int MAX_BLOCK_SIZE = 1000000; if you disagree then please explain further

Soooooooon...............
GlitterRush
Jr. Member
*
Offline Offline

Activity: 56
Merit: 10


View Profile
March 08, 2015, 10:38:44 AM
 #563

i am going to buy some bitz now see how this goes

Get your TAM today at https://c-cex.com/?p=tam-btc
drays
Legendary
*
Offline Offline

Activity: 2520
Merit: 1073


View Profile
March 08, 2015, 01:44:39 PM
 #564

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

Well, it is not a 100% conclusion, but more of a guess based on few factors:
Here they are:
1. There is no limitation in the function where it is usually set: in GetProofOfWorkReward()
2. Dev (you) did not point to the exact place in the code where the limitation it is set (the only value in main.h equal to 1000000, is MAX_BLOCK_SIZE, which has nothing to do with PoW block limitation as far as I know)
3. No other places found during basic search...

Still, I have no problem accepting you are right and there is a limitation, but please show that, if it is indeed there. I am not FUD'ding, and definitely have nothing against your coin, its just interesting for me as a programmer; though I have extensive c++ background, I am not very familiar with qt-wallet structure Smiley



It should be static const unsigned int MAX_BLOCK_SIZE = 1000000; if you disagree then please explain further

This is completely different parameter. It is just the max size of a single block (in bytes), as explained here for example: https://bitcointalk.org/index.php?topic=122009.msg1312701#msg1312701. It is not used to limit the number of blocks.

... this space is not for rent ...
SalimNagamato
Legendary
*
Offline Offline

Activity: 924
Merit: 1000



View Profile
March 08, 2015, 01:53:25 PM
 #565

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

Well, it is not a 100% conclusion, but more of a guess based on few factors:
Here they are:
1. There is no limitation in the function where it is usually set: in GetProofOfWorkReward()
2. Dev (you) did not point to the exact place in the code where the limitation it is set (the only value in main.h equal to 1000000, is MAX_BLOCK_SIZE, which has nothing to do with PoW block limitation as far as I know)
3. No other places found during basic search...

Still, I have no problem accepting you are right and there is a limitation, but please show that, if it is indeed there. I am not FUD'ding, and definitely have nothing against your coin, its just interesting for me as a programmer; though I have extensive c++ background, I am not very familiar with qt-wallet structure Smiley



It should be static const unsigned int MAX_BLOCK_SIZE = 1000000; if you disagree then please explain further

MAX_BLOCK_SIZE is the maximum size of a block in bytes. AFAIK

not hashing, folding and curing (check FLDC merged-folding! reuse good GPUs)
drays
Legendary
*
Offline Offline

Activity: 2520
Merit: 1073


View Profile
March 08, 2015, 01:58:04 PM
 #566

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

There is no end to a POW coin. The reward just get down to where you are just mining the transaction fees.

So do you think there is no need to limit the reward starting from 1000000, as stated in OP?

I was thinking it might make sense to replace this:

Quote
int64_t GetProofOfWorkReward(int64_t nFees)
{
   int64_t nSubsidy = 35 * COIN;
   if (fDebug && GetBoolArg("-printcreation"))
      printf("GetProofOfWorkReward() : create=%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
   return nSubsidy + nFees;
}

by this

Quote
int64_t GetProofOfWorkReward(int64_t nFees)
{
   int64_t nSubsidy = 0 * COIN;
   if (pindexBest->nHeight+1 <= 1000000)
   {
      nSubsidy = 35 * COIN;
   }

   if (fDebug && GetBoolArg("-printcreation"))
      printf("GetProofOfWorkReward() : create=%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
   
   return nSubsidy + nFees;
}

So it matches the description in OP...

Otherwise it would give 35 coins (+fees) per block forever, isn't it..?

... this space is not for rent ...
SalimNagamato
Legendary
*
Offline Offline

Activity: 924
Merit: 1000



View Profile
March 08, 2015, 02:01:35 PM
 #567

also MAX_MONEY is only 18000000
should be fixed as well unless im wrong

not hashing, folding and curing (check FLDC merged-folding! reuse good GPUs)
SalimNagamato
Legendary
*
Offline Offline

Activity: 924
Merit: 1000



View Profile
March 08, 2015, 02:02:10 PM
 #568

Specs.
Algo: X11 Pow/PoS hybrid
Total number of coins: ~45.000.000 after eons of time
PoW ends at block 1000000: ~ 35.000.000 coins
Coins rewarded per block (PoW): 35
Time per block: ~ 1 minute
Difficulty Re-target: 10-20 minutes
PoS 10% per year from block 0


where in the code does it say, about last POW block is 1000000 ?
help me find it please

Hmmm... Thats good question... I guess the correct answer is - nowhere  Undecided
The number of PoW blocks is not limited, so either the Dev doesn't think the coin will exist for so long time, or a hard fork with mandatory wallet update is coming soon...

So, please explain how you reached the conclusion that there is no end to the POW?

There is no end to a POW coin. The reward just get down to where you are just mining the transaction fees.

So do you think there is no need to limit the reward starting from 1000000, as stated in OP?

I was thinking it might make sense to replace this:

Quote
int64_t GetProofOfWorkReward(int64_t nFees)
{
   int64_t nSubsidy = 35 * COIN;
   if (fDebug && GetBoolArg("-printcreation"))
      printf("GetProofOfWorkReward() : create=%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
   return nSubsidy + nFees;
}

by this

Quote
int64_t GetProofOfWorkReward(int64_t nFees)
{
   int64_t nSubsidy = 0 * COIN;
   if (pindexBest->nHeight+1 <= 1000000)
   {
      nSubsidy = 35 * COIN;
   }

   if (fDebug && GetBoolArg("-printcreation"))
      printf("GetProofOfWorkReward() : create=%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
   
   return nSubsidy + nFees;
}

So it matches the description in OP...

Otherwise it would give 35 coins (+fees) per block forever, isn't it..?

you will need hard fork for this. and probably reject old clients

not hashing, folding and curing (check FLDC merged-folding! reuse good GPUs)
drays
Legendary
*
Offline Offline

Activity: 2520
Merit: 1073


View Profile
March 08, 2015, 02:12:16 PM
Last edit: March 08, 2015, 02:31:00 PM by drays
 #569

also MAX_MONEY is only 18000000
should be fixed as well unless im wrong

MAX_MONEY should be ok, as far as I understand. It does not limit the total number of coins. Here is some info from the net: "MAX_MONEY is only used as a sanity check to prevent "impossible" transactions and integer overflows (any transaction sending more than MAX_MONEY is invalid, regardless of all other factors)."

you will need hard fork for this. and probably reject old clients

Yes, hard fork will be needed (of course if the Dev considers the block height reward limitation to be important), as I wrote in my first post... But it will not harm anything actually, if done correctly.

... this space is not for rent ...
SalimNagamato
Legendary
*
Offline Offline

Activity: 924
Merit: 1000



View Profile
March 08, 2015, 02:17:03 PM
 #570

also MAX_MONEY is only 18000000
should be fixed as well unless im wrong

MAX_MONEY should be ok, as far as I understand. It does not limit the number of coins. Here is some info from the net: "MAX_MONEY is only used as a sanity check to prevent "impossible" transactions and integer overflows (any transaction sending more than MAX_MONEY is invalid, regardless of all other factors)."

you will need hard fork for this. and probably reject old clients

Yes, hard fork will be needed (of course if the Dev considers the block height reward limitation to be important), as I wrote in my first post... But it will not harm anything actually, if done correctly.

what can limits the cap ? to 45000000 of POS+POW
any bounty for alerting about the limitless POW bug ? Smiley
thanks

not hashing, folding and curing (check FLDC merged-folding! reuse good GPUs)
EBK1000 (OP)
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000


A Wound in Eternity


View Profile
March 08, 2015, 05:24:19 PM
 #571

Give me a couple of days to consider what to do and I will update. This doesn't affect things in the short term. We will sort it and I will get back with a solution and a plan.

Soooooooon...............
EBK1000 (OP)
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000


A Wound in Eternity


View Profile
March 08, 2015, 05:58:59 PM
 #572

I have added a poll to get some opinion as to when the PoW should end.

Soooooooon...............
DonQuijote
Legendary
*
Offline Offline

Activity: 1551
Merit: 1002


♠ ♥ ♣ ♦ < ♛♚&#


View Profile
March 09, 2015, 08:17:06 PM
 #573

I have added a poll to get some opinion as to when the PoW should end.
Thanks dev!

THE INGENIOUS GENTLEMAN DON QUIXOTE OF LA MANCHA
♠ ♥ ♣ ♦ < ♛♚♝♞♜ BTC tip: 39gUUFdJBdKWXnLoh3PMNX9eUz3DwakBKq
EBK1000 (OP)
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000


A Wound in Eternity


View Profile
March 10, 2015, 06:32:51 AM
 #574

There aren't many people voting but as it stands the PoW will end at block 500,000 and then it will pure PoS from that point on.

Soooooooon...............
Matt9301
Legendary
*
Offline Offline

Activity: 1554
Merit: 1008


View Profile
March 10, 2015, 09:48:39 AM
 #575

where can buy BITZ/ ?  Huh Huh Huh Grin Grin Smiley Smiley Smiley

Here you can: https://yobit.net/en/trade/BITZ/BTC
rnameltc
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
March 10, 2015, 10:06:58 AM
 #576

I'm a bit worried about the lack of development and the fact that BITZ didn't hit any other exchange except Yobit where the trading volume is zero. I think that there is a lot of potential here and the DEV will turn the things around be he should act a bit faster.
speedy1987
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


View Profile
March 10, 2015, 10:09:15 AM
 #577

It is only 14 days old coin.
At least yobit is an option.
More exchanges will come through voting.
provenceday
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000



View Profile
March 10, 2015, 10:18:13 AM
 #578

how about CCEX or Bittrex?

thanks!
rnameltc
Member
**
Offline Offline

Activity: 93
Merit: 10


View Profile
March 10, 2015, 01:46:37 PM
 #579


Yeah, I know, but addition on C-cex is not that hard as there is a community build here. I don't know if it's in DEV's plan and he is doing now.
EBK1000 (OP)
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000


A Wound in Eternity


View Profile
March 10, 2015, 07:12:31 PM
 #580


Yeah, I know, but addition on C-cex is not that hard as there is a community build here. I don't know if it's in DEV's plan and he is doing now.

My plan is first and foremost to implement the PoW stop at block 500,000. Once that is done, hopefully in a week or two, we will have a stable and permanent blockchain. New wallets will be released and once that is done, I will concentrate on getting some more exchanges and take it from there. I am not so worried about time as this is a long term thing and I will build on it as soon as some teething problems have been sorted. Don't worry about me leaving this project.

C-cex will come when there is enough votes, I am not planning to pay a high price to get it listed now. Bittrex will come as well.

Soooooooon...............
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29] 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!