[BTE] The Bytecoin Information Thread - page 4.

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 09, 2024, 03:47:15 AM

Quote from: movellan on May 08, 2024, 03:04:14 PM

Quote from: cpu6502 on May 08, 2024, 12:18:19 PM

Quote from: movellan on May 08, 2024, 11:28:18 AM

Sorry, no forks accepted. Original blockchain only, please. Your subsequent messages indicate only self-interest in the mining efforts of others. Bad form, old chap.

I don't really understand.

It is the original mainnet blockchain. I only mined onto the end of the stalled chain (stalled for years); first of all using the outdated version 0.8.1 and later when upgraded it to the modern 27.0 version. 1:1 copy still. (Except a few technical changes, such as addresses, magic bytes, ports etc...)

Any coins you, and anyone else, earned/mined years ago will still be spendable.

OK, I'll bite. Do you have a windows compiled release?

Well it's been a while since I've done any cross compiling (window binary built from inside linux), but I'll give it a go.
Give me a little while to figure it out, I'm confident I can do it.

Sounds good.

cpu6502

jr. member

Activity: 82

Merit: 1

Quote from: movellan on May 08, 2024, 03:04:14 PM

Quote from: cpu6502 on May 08, 2024, 12:18:19 PM

Quote from: movellan on May 08, 2024, 11:28:18 AM

Sorry, no forks accepted. Original blockchain only, please. Your subsequent messages indicate only self-interest in the mining efforts of others. Bad form, old chap.

I don't really understand.

It is the original mainnet blockchain. I only mined onto the end of the stalled chain (stalled for years); first of all using the outdated version 0.8.1 and later when upgraded it to the modern 27.0 version. 1:1 copy still. (Except a few technical changes, such as addresses, magic bytes, ports etc...)

Any coins you, and anyone else, earned/mined years ago will still be spendable.

OK, I'll bite. Do you have a windows compiled release?

Well it's been a while since I've done any cross compiling (window binary built from inside linux), but I'll give it a go.
Give me a little while to figure it out, I'm confident I can do it.

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 08, 2024, 12:18:19 PM

Quote from: movellan on May 08, 2024, 11:28:18 AM

Sorry, no forks accepted. Original blockchain only, please. Your subsequent messages indicate only self-interest in the mining efforts of others. Bad form, old chap.

I don't really understand.

It is the original mainnet blockchain. I only mined onto the end of the stalled chain (stalled for years); first of all using the outdated version 0.8.1 and later when upgraded it to the modern 27.0 version. 1:1 copy still. (Except a few technical changes, such as addresses, magic bytes, ports etc...)

Any coins you, and anyone else, earned/mined years ago will still be spendable.

OK, I'll bite. Do you have a windows compiled release?

cpu6502

jr. member

Activity: 82

Merit: 1

Quote from: movellan on May 08, 2024, 11:28:18 AM

Sorry, no forks accepted. Original blockchain only, please. Your subsequent messages indicate only self-interest in the mining efforts of others. Bad form, old chap.

I don't really understand.

It is the original mainnet blockchain. I only mined onto the end of the stalled chain (stalled for years); first of all using the outdated version 0.8.1 and later when upgraded it to the modern 27.0 version. 1:1 copy still. (Except a few technical changes, such as addresses, magic bytes, ports etc...)

Any coins you, and anyone else, earned/mined years ago will still be spendable.

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 02, 2024, 03:23:58 AM

Quote from: movellan on May 02, 2024, 02:16:46 AM

Thanks \for replying.

Is your release based on the original BTE implementation or Ahmed Bodi's fork?

Originally I tried to merge the latest bitcoin version into both of these. But v27 is so far away from v0.8, with thousands of git commits; I just got tied up in knots.

I tried a different approach. Forked bitcoin v27.0 and just made the bytecoin changes to that; genesis block, port numbers etc...
Found this way much easier. Hopefully moving up to v28.0 should be easy, with just a smaller number of commits to merge.

Mainnet is the original chain still of course, block 75306 at time of writing. But I never had a copy of the testnet chain, so I started a new one; block 21907 currently. It's only the testnet so I guess that doesn't matter.

So the answer to your question is neither I guess. It's based on bitcoin v27.0

Sorry, no forks accepted. Original blockchain only, please. Your subsequent messages indicate only self-interest in the mining efforts of others. Bad form, old chap.

cpu6502

jr. member

Activity: 82

Merit: 1

Also got the testnet with solo mining fixed up now as well. 2% fee again. Starting diff 1.

Code:

stratum+tcp://bytecoin.testnet.pool.chainspy.com:2001

cpu6502

jr. member

Activity: 82

Merit: 1

You cannot mine directly to a bytecoin core node, so I have set up a public solo mining pool for easier mining.
There is currently three running, each with different starting diffs:

Diff 1: stratum+tcp://bytecoin.pool.chainspy.com:3001
Diff 1000: stratum+tcp://bytecoin.pool.chainspy.com:3004
Diff 10000: stratum+tcp://bytecoin.pool.chainspy.com:3005

Set your username to your bytecoin address with any or even no worker extension, and any password.
eg:

Code:

cgminer -o stratum+tcp://bytecoin.pool.chainspy.com:3004 -u bytec1q9ny3xycmfrfev2xquun64sunvvh2zlx2gn63xz.0 -p x

If you enter an invalid address you will be rejected.
2% fee for using the pool which is sent to bytec1q9ny3xycmfrfev2xquun64sunvvh2zlx2gn63xz

Remember this is a solo mining, so you only get a reward if you're the one to find a valid block.
Difficulty is currently at 7790.512516801227 which is really low. 55.77GH/s gives an average 10 minute block time.

cpu6502

jr. member

Activity: 82

Merit: 1

Also for ipv6 users, bytecoin nodes are running at:

[2a01:7e00::f03c:93ff:fe91:6c70]:6333 for mainnet
[2a01:7e00::f03c:93ff:fe91:6c70]:16333 for testnet

cpu6502

jr. member

Activity: 82

Merit: 1

When compiling bytecoin I would like the final binaries to be called bytecoind and bytecoin-qt, but I'm having trouble implementing this. It keeps compiling to bitcoind and bitcoin-qt, which is annoying.
Of course they could be renamed afterwards, but that's more of a work around than done properly.

cpu6502

jr. member

Activity: 82

Merit: 1

Quote from: movellan on May 02, 2024, 02:16:46 AM

Thanks \for replying.

Is your release based on the original BTE implementation or Ahmed Bodi's fork?

Originally I tried to merge the latest bitcoin version into both of these. But v27 is so far away from v0.8, with thousands of git commits; I just got tied up in knots.

I tried a different approach. Forked bitcoin v27.0 and just made the bytecoin changes to that; genesis block, port numbers etc...
Found this way much easier. Hopefully moving up to v28.0 should be easy, with just a smaller number of commits to merge.

Mainnet is the original chain still of course, block 75306 at time of writing. But I never had a copy of the testnet chain, so I started a new one; block 21907 currently. It's only the testnet so I guess that doesn't matter.

So the answer to your question is neither I guess. It's based on bitcoin v27.0

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 01, 2024, 05:48:45 PM

Quote from: movellan on February 18, 2024, 02:34:47 AM

Ran my Bytecoin 0.8.1.0 client this morning and received an "Alert key compromised, upgrade required" error message. Anyone know what this is about? TIA.

This is a really old version; alert keys were deprecated way back in 2018 I think. You can ignore the message.

Best to upgrade to the newest version of bytecoin (v27.0.0); based on bitcoin v27.0.
I've just released it here: https://github.com/bytecoin-crypto/bytecoin

You can connect to bytecoin mainnet node at 178.79.133.60:6333 and a bytecoin testnet node at 178.79.133.60:16333

Make sure you backup any old wallet(s) before importing them into the new version, just in case it corrupts it.

Thanks \for replying.

Is your release based on the original BTE implementation or Ahmed Bodi's fork?

cpu6502

jr. member

Activity: 82

Merit: 1

Quote from: movellan on February 18, 2024, 02:34:47 AM

Ran my Bytecoin 0.8.1.0 client this morning and received an "Alert key compromised, upgrade required" error message. Anyone know what this is about? TIA.

This is a really old version; alert keys were deprecated way back in 2018 I think. You can ignore the message.

Best to upgrade to the newest version of bytecoin (v27.0.0); based on bitcoin v27.0.
I've just released it here: https://github.com/bytecoin-crypto/bytecoin

You can connect to bytecoin mainnet node at 178.79.133.60:6333 and a bytecoin testnet node at 178.79.133.60:16333

Make sure you backup any old wallet(s) before importing them into the new version, just in case it corrupts it.

movellan

full member

Activity: 368

Merit: 100

Ran my Bytecoin 0.8.1.0 client this morning and received an "Alert key compromised, upgrade required" error message. Anyone know what this is about? TIA.

movellan

full member

Activity: 368

Merit: 100

Hey Prof, are you mining again?

movellan

full member

Activity: 368

Merit: 100

Bryan Mills' original implementation is here,

https://github.com/bryan-mills/bytecoin

Ahmed Bodi's attempted fork is here,

https://github.com/ahmedbodi/bytecoin

Not sure if this fork was ever attempted/implemented.

dbkeys

full member

Activity: 486

Merit: 104

Quote from: movellan on February 10, 2022, 01:04:07 AM

Quote from: dbkeys on February 08, 2022, 07:35:23 PM

Quote from: movellan on February 07, 2022, 08:01:27 AM

86.131.40.79 looks good and connects as a peer.

188.213.34.67 also appears to connect as a peer.

I cannot connect to 172.31.47.236 or 164.68.101.222.

It still can't find good nodes ...
I wonder if the chain parameters I'm using are correct.
There seem to be two bytecoins out there at least; where is the latest code for this blockchain?

188.213.34.67 no longer connects.

"Two bytecoins". Two possibilities here.

1) Pre-mined shitcoin calling itself "bytecoin". Usually differentiated as "BCN" versus "BTE", the real Bytecoin.

2) Ahmed Bodi tried to fork BTE. I've never seen any evidence that he succeeded.

What "latest code" are you looking for?

Looking for the source code to BTE the "real" Bytecoin. In other words, the reference implementation, or any "correct" implementation.

movellan

full member

Activity: 368

Merit: 100

Quote from: dbkeys on February 08, 2022, 07:35:23 PM

Quote from: movellan on February 07, 2022, 08:01:27 AM

86.131.40.79 looks good and connects as a peer.

188.213.34.67 also appears to connect as a peer.

I cannot connect to 172.31.47.236 or 164.68.101.222.

It still can't find good nodes ...
I wonder if the chain parameters I'm using are correct.
There seem to be two bytecoins out there at least; where is the latest code for this blockchain?

188.213.34.67 no longer connects.

"Two bytecoins". Two possibilities here.

1) Pre-mined shitcoin calling itself "bytecoin". Usually differentiated as "BCN" versus "BTE", the real Bytecoin.

2) Ahmed Bodi tried to fork BTE. I've never seen any evidence that he succeeded.

What "latest code" are you looking for?

dbkeys

full member

Activity: 486

Merit: 104

Quote from: movellan on February 07, 2022, 08:01:27 AM

86.131.40.79 looks good and connects as a peer.

188.213.34.67 also appears to connect as a peer.

I cannot connect to 172.31.47.236 or 164.68.101.222.

It still can't find good nodes ...
I wonder if the chain parameters I'm using are correct.
There seem to be two bytecoins out there at least; where is the latest code for this blockchain?

movellan

full member

Activity: 368

Merit: 100

86.131.40.79 looks good and connects as a peer.

188.213.34.67 also appears to connect as a peer.

I cannot connect to 172.31.47.236 or 164.68.101.222.

dbkeys

full member

Activity: 486

Merit: 104

Quote from: movellan on February 06, 2022, 02:34:11 AM

Code:

dbkeys@home ~ % dig bte.chainetics.com
;; ANSWER SECTION:
bte.chainetics.com.	3420	IN	A	86.160.129.103

IP is not valid for a node.

Do you have a list of good, valid nodes I can prime the tracker/seeder with ?

These are the IP's the tracker/seeder is primed with right now ( I removed the IP you said is invalid ):

Code:

 // At least one valid seed ip address is required to begin crawling the network
 seed_1="164.68.101.222"         // https://bitcointalk.org/index.php?topic=169559.680
 seed_2="172.31.47.236"
 seed_3="86.131.40.79"

Once it latches on to the P2P network, the Node Tracker / DNS Seeder will maintain a real-time list of good nodes which accept connections.

These are the blockchain parameters programmed into the node tracker:

Code:

 

//  BlockChain parameters and Protocol version numbers
//--------------------------------------------------------------------------------------------------------------------------------------/
blockchain_name="Bytecoin"      //
ticker="BTE"
protocol_version="70001"        // --- Typically, these are found ( protocol version,init_proto_version, etc)  in the coin's version.h file
init_proto_version="209"        //
min_peer_proto_version="209"    //        Leave blank or set to the same value as protocol_version if not applicable in your blockchain
caddr_time_version="31402"      //
pchMessageStart_0 = "0x0b"      // --- Typically you can find the 4 pchMessageStart values in your coin's main.cpp or chainparams.cpp file
pchMessageStart_1 = "0x22"      //      ByteCoin: main.cpp pchMessageStart[0]..[3]
pchMessageStart_2 = "0x03"      //
pchMessageStart_3 = "0x14"      //
wallet_port="6333"              // P2P port: The coin servers's main port
block_count="64754"             // A node cannot be considered "good" unless it has a block height greater or equal to this value.
host="bte.chainetics.com"       // -h parameter : subdomain to query

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