Pages:
Author

Topic: [BTE] The Bytecoin Information Thread - page 39. (Read 80193 times)

legendary
Activity: 2632
Merit: 1023
April 08, 2013, 12:34:34 AM
#26
You forgot to mention to Premine by large block regarding in the beginning
sr. member
Activity: 462
Merit: 250
sr. member
Activity: 490
Merit: 254
April 07, 2013, 09:03:29 PM
#24
Added BTE Hashers Pool.
sr. member
Activity: 490
Merit: 254
April 07, 2013, 06:59:02 PM
#23
hi bte family

I was wondering are there any ideas to help against asic 51% attacks?  I don't quite have the know-how to code yet, but I feel if someone could figure out how to take the 51% attack vulnerability the coin would have a guaranteed bright future.

I have been dabbling in terracoin, and the 51% attacks have been making my stomach drop to my toes, and I think alot of stomachs dropped to alot of toes actually.

just throwing it out there for development stimulus.  the first innovator to figure out 51% protection will be a bte hero

It is so new that nothing is guaranteed. I am by no means an expert in any of this, but from what I have read I would think the best defense, which I believe we have going at least so far, is plenty of miners and plenty of pools. The more pools, and miners that are hopefully distributed evenly among these pools, we have the harder it would be for a individual or small group to come in and dominate the field, thus attempting a 51% attack.

I also think it is in the best interest of the pools to look out for this as well. My bitcoin miners participate in the BTC Guild pool, and I have seen they have a plan in place to try and discourage gaining too large of a membership. Basically, they plan to raise the pool fees if the pool hash rates start to go over 40% of the network hash rate.  They recognize that people will be scared off and lose confidence in bitcoin should one pool even approach 51% of processing power. It is in the best interests of everyone to try and avoid this scenario.

This same approach will also need to apply to bytecoin, since it is basically a 1:1 derivative of the bitcoin code. If enough people stick with it and pools and miners continue to be brought on board, in approximately proportional ratios, I think it may have a good chance of surviving. But only time will tell...
sr. member
Activity: 490
Merit: 254
April 07, 2013, 05:40:58 PM
#22
Added a fix for p2pool bytecoin until its gets hardcoded into the main tree

Fix makes sure your local p2pool find other pools instead of beeing alone in the dark.

https://bitcointalksearch.org/topic/howto-setup-a-p2pool-for-bytecoin-169910

Added.
member
Activity: 112
Merit: 10
We are connected. you are me I am you.
April 07, 2013, 05:38:56 PM
#21
hi bte family

I was wondering are there any ideas to help against asic 51% attacks?  I don't quite have the know-how to code yet, but I feel if someone could figure out how to take the 51% attack vulnerability the coin would have a guaranteed bright future.

I have been dabbling in terracoin, and the 51% attacks have been making my stomach drop to my toes, and I think alot of stomachs dropped to alot of toes actually.

just throwing it out there for development stimulus.  the first innovator to figure out 51% protection will be a bte hero
full member
Activity: 126
Merit: 100
April 07, 2013, 05:14:34 PM
#20
See this re source - https://bitcointalk.org/index.php?topic=169236.msg1760297;topicseen#msg1760297

If you look through my diff, you can see that they swapped bitcoin for bytecoin everywhere in the code

And I think this is where its a different blockchain ( genesis block ) :


diff -r src.bit/main.cpp src.byte/main.cpp
34c34
< uint256 hashGenesisBlock("0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f");
---
> uint256 hashGenesisBlock("0x00000000c3040b997c96926200ed00b0a5b2e97e3d0015deb41249489e666f84");
62c62
< const string strMessageMagic = "Bitcoin Signed Message:\n";
---
> const string strMessageMagic = "Bytecoin Signed Message:\n";
1597,1603c1597,1598
<     // This rule was originally applied all blocks whose timestamp was after March 15, 2012, 0:00 UTC.
<     // Now that the whole chain is irreversibly beyond that time it is applied to all blocks except the
<     // two in the chain that violate it. This prevents exploiting the issue against nodes in their
<     // initial block download.
<     bool fEnforceBIP30 = (!pindex->phashBlock) || // Enforce on CreateNewBlock invocations which don't have a hash.
<                           !((pindex->nHeight==91842 && pindex->GetBlockHash() == uint256("0x00000000000a4d0a398161ffc163c503763b1f4360639393e0e4c8e300e0caec")) ||
<                            (pindex->nHeight==91880 && pindex->GetBlockHash() == uint256("0x00000000000743f190a18c5577a3c2d2a1f610ae9601ac046a38084ccb7cd721")));
---
>
>     bool fEnforceBIP30 = true;
full member
Activity: 196
Merit: 100
April 07, 2013, 05:05:14 PM
#19
One thing I'd like to see... If ByteCoin is ... 100% identical to BitCoin ... Why isnt it mining and processing BTC/BitCoins .. Where is the source difference that specifies ... to be a new blockchain ?
legendary
Activity: 1722
Merit: 1217
April 07, 2013, 05:04:40 PM
#18
full member
Activity: 196
Merit: 100
April 07, 2013, 05:01:45 PM
#17
        const char* pszTimestamp = "04/01/2013 ABC News: North Korea pledges to expand nuclear program.";
        CTransaction txNew;
        txNew.vin.resize(1);
        txNew.vout.resize(1);
        txNew.vin[0].scriptSig = CScript() << 486604799 << CBigNum(4) << vector((const unsigned char*)pszTimestamp, (const unsigned char*)pszTimestamp + strlen(pszTimestamp));
        txNew.vout[0].nValue = 50 * COIN;
        txNew.vout[0].scriptPubKey = CScript() << ParseHex("04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f") << OP_CHECKSIG;
        CBlock block;
        block.vtx.push_back(txNew);
        block.hashPrevBlock = 0;
        block.hashMerkleRoot = block.BuildMerkleTree();
        block.nVersion = 2;
        block.nTime    = 1364786987;
        block.nBits    = 0x1d00ffff;
        block.nNonce   = 29849213;

^^ for ByteCoin

versus

        const char* pszTimestamp = "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks";
        CTransaction txNew;
        txNew.vin.resize(1);
        txNew.vout.resize(1);
        txNew.vin[0].scriptSig = CScript() << 486604799 << CBigNum(4) << vector((const unsigned char*)pszTimestamp, (const unsigned char*)pszTimestamp + strlen(pszTimestamp));
        txNew.vout[0].nValue = 50 * COIN;
        txNew.vout[0].scriptPubKey = CScript() << ParseHex("04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f") << OP_CHECKSIG;
        CBlock block;
        block.vtx.push_back(txNew);
        block.hashPrevBlock = 0;
        block.hashMerkleRoot = block.BuildMerkleTree();
        block.nVersion = 1;
        block.nTime    = 1231006505;
        block.nBits    = 0x1d00ffff;
        block.nNonce   = 2083236893;

For BitCoin

been checking out the diff in those two files. Most relate to the genesis block and the BIP30 03/22 check
sr. member
Activity: 490
Merit: 254
April 07, 2013, 04:20:05 PM
#16
thanks so much! its just to hold us over until get a real exchange.

You're Welcome! Thanks for the update to the list.
legendary
Activity: 1722
Merit: 1217
April 07, 2013, 04:14:43 PM
#15
thanks so much! its just to hold us over until get a real exchange.
full member
Activity: 196
Merit: 100
April 07, 2013, 04:13:00 PM
#14
Thanks for adding our faucet. I've added the other faucet to the site/rotation.

We need more BTE Sites!

Also this https://bitcointalksearch.org/topic/bytecoin-081-client-mirrors-168538 (all binaries+source all os for BTE Clients)

Also now paying 10 uBTE per submit Smiley

Added the client mirror list and gave you credit for that section BitHits. If that is not ok I can remove it and simply link to your post.

Yes the more people with the client list the better Tongue

Also can you update the faucet list to reflect 10 uBTE // 0.00001 BTE for www.ByteHits.info Smiley
sr. member
Activity: 490
Merit: 254
April 07, 2013, 04:06:47 PM
#13
Thanks for adding our faucet. I've added the other faucet to the site/rotation.

We need more BTE Sites!

Also this https://bitcointalksearch.org/topic/bytecoin-081-client-mirrors-168538 (all binaries+source all os for BTE Clients)

Also now paying 10 uBTE per submit Smiley

Added the client mirror list and gave you credit for that section BitHits. If that is not ok I can remove it and simply link to your post.
donator
Activity: 362
Merit: 250
April 07, 2013, 03:52:41 PM
#11
so wait, is the cap 81 million or 21 million?

21 Million. Same as Bitcoin.

I've seen various places say it's 81 million. Do you have a source? Or.. Can you point me to the line in the source code that specifies this, that would pretty much settle the matter Tongue

Yea I'm looking for some proof!

It's right here, same as bitcoin -

https://github.com/bryan-mills/bytecoin/blob/0.8.1/src/main.cpp#L1053

https://github.com/bitcoin/bitcoin/blob/0.8.1/src/main.cpp#L1053
legendary
Activity: 1611
Merit: 1001
April 07, 2013, 03:44:58 PM
#10
so wait, is the cap 81 million or 21 million?

21 Million. Same as Bitcoin.

I've seen various places say it's 81 million. Do you have a source? Or.. Can you point me to the line in the source code that specifies this, that would pretty much settle the matter Tongue

Yea I'm looking for some proof!
full member
Activity: 196
Merit: 100
April 07, 2013, 03:44:36 PM
#9
so wait, is the cap 81 million or 21 million?

21 Million. Same as Bitcoin.

I've seen various places say it's 81 million. Do you have a source? Or.. Can you point me to the line in the source code that specifies this, that would pretty much settle the matter Tongue
member
Activity: 70
Merit: 10
April 07, 2013, 03:43:20 PM
#8
so wait, is the cap 81 million or 21 million?

21 Million. Same as Bitcoin.
Pages:
Jump to: