movellan
|
|
December 06, 2021, 05:27:18 AM Last edit: December 06, 2021, 06:57:42 PM by mprep |
|
No luck on that one. Send me another and then also the next couple of times it changes. I may be able to specify a IP range if the address are close enough to each other. If you can get your node running, PM your IP address and I'll try and connect. If you don't mind making your IP public, you can post it her and perhaps others can connect also. LMK. If you don't have the Windows wallet setup, I can supply a clean copy. Shouldn't take long to DL the entire blockchain. Hi ya, I'm trying to reconstruct my transactions from years ago. Tax reasons. There's a lot, and many exchanges are now defunct and so with it my trade records. I have an old bytecoin BTE wallet, and have compiled the bytecoin daemon, but unable to download the blockchain as there is currently no peers. Can anyone help with this? My ip is currently 86.160.129.103 but my ISP changes it regularly, so it may of changed by the time you read this. I have a DDNS address setup at dns1.ddns.net which should still point to me if my ISP changes it. I have my node running and listening on port 6333 and have opened up the port in my firewall. Hope you can connect.
OK, it's connected now. As per previous message keep me abreast of your IP changes until I can get a working IP range going. If you can get your node running, PM your IP address and I'll try and connect. If you don't mind making your IP public, you can post it her and perhaps others can connect also. LMK. If you don't have the Windows wallet setup, I can supply a clean copy. Shouldn't take long to DL the entire blockchain. Hi ya, I'm trying to reconstruct my transactions from years ago. Tax reasons. There's a lot, and many exchanges are now defunct and so with it my trade records. I have an old bytecoin BTE wallet, and have compiled the bytecoin daemon, but unable to download the blockchain as there is currently no peers. Can anyone help with this? My ip is currently 86.160.129.103 but my ISP changes it regularly, so it may of changed by the time you read this. I have a DDNS address setup at dns1.ddns.net which should still point to me if my ISP changes it. I have my node running and listening on port 6333 and have opened up the port in my firewall. Hope you can connect. [moderator's note: consecutive posts merged]
|
|
|
|
cpu6502
Jr. Member
Offline
Activity: 68
Merit: 1
|
|
December 06, 2021, 08:18:07 PM |
|
Got the blockchain now Thank you very much indeed. That helps me plenty, as I can now see I sent BTE coins to (probably) an exchange in early May 2013, presumably I exchanged for BTC I'm guessing. I can now fill in a blank space on my transactions. There's plenty more missing gaps though. Don't suppose you've got the blockchains for Fairbrix and Tenebrix as well? Leaked transaction trade dumps of btc-e.com and cryptsy.com would be a life saver, but I can't find those anyway on the web. So wished I'd exported my trade data before the sites went down. Anyway, once again thank you very much.
|
|
|
|
realdantreccia
|
|
January 31, 2022, 09:39:38 PM |
|
Got the blockchain now Thank you very much indeed. That helps me plenty, as I can now see I sent BTE coins to (probably) an exchange in early May 2013, presumably I exchanged for BTC I'm guessing. I can now fill in a blank space on my transactions. There's plenty more missing gaps though. Don't suppose you've got the blockchains for Fairbrix and Tenebrix as well? Leaked transaction trade dumps of btc-e.com and cryptsy.com would be a life saver, but I can't find those anyway on the web. So wished I'd exported my trade data before the sites went down. Anyway, once again thank you very much. Got the blockchain now Thank you very much indeed. That helps me plenty, as I can now see I sent BTE coins to (probably) an exchange in early May 2013, presumably I exchanged for BTC I'm guessing. I can now fill in a blank space on my transactions. There's plenty more missing gaps though. Don't suppose you've got the blockchains for Fairbrix and Tenebrix as well? Leaked transaction trade dumps of btc-e.com and cryptsy.com would be a life saver, but I can't find those anyway on the web. So wished I'd exported my trade data before the sites went down. Anyway, once again thank you very much. Got the blockchain now Thank you very much indeed. That helps me plenty, as I can now see I sent BTE coins to (probably) an exchange in early May 2013, presumably I exchanged for BTC I'm guessing. I can now fill in a blank space on my transactions. There's plenty more missing gaps though. Don't suppose you've got the blockchains for Fairbrix and Tenebrix as well? Leaked transaction trade dumps of btc-e.com and cryptsy.com would be a life saver, but I can't find those anyway on the web. So wished I'd exported my trade data before the sites went down. Anyway, once again thank you very much. I have Tenebrix mining and up to the latest block . What files do you need? Also, I'm successfully syncing BTE blocks! Thanks for the nodes guys. What is the goal here with Bytecoin? If anyone wants to donate me my first BTE I have TBX to share - 607,000+ TBX total haha. BTE: 8JtibXCVjX8tvCZ9S3Z2vDPyAk3bmNzP25
|
From the many one, from one, the source
|
|
|
movellan
|
|
February 01, 2022, 11:45:25 AM |
|
How about sharing the nodes?
|
|
|
|
dbkeys
|
|
February 05, 2022, 04:00:46 PM |
|
It does not say anywhere who created this coin and why. Also how much preminning happened with this coin?
Check here https://bitcointalk.org/index.php?topic=164569.0Bytecoin was launched with no pre-mining, but almost immediately a guy who goes by Ahmed Bodi from BC, Canada (I think) pointed a big ASIC at the coin. He and his gang scarfed over 100,000 BTE during the first year from startup. He would mine until the difficulty went up, wait till it dropped at the next recalc, mine again and so on. He did this at least half a dozen times, but then seemed to lose interest. We have had several posters on this thread recently that I suspect are Bodi or one of his associates posing as newbies under different handles. Difficulty is now down to 264k, so now is a good time to start mining. This coin evidently needs a hardfork to a more responsive diffalgo (like Dark Gravity Wave, etc.) Tried to compile a node, but the code is quite obsolete ... lots of errors related to new SSL library / BIGNUM. I did set up a node tracker / DNS seeder for fun, with the few IP's I found on the thread; but so far it has not found any novel nodes, it just gives back the hard coded IP from this thread: dbkeys@home ~ % dig bte.chainetics.com ;; ANSWER SECTION: bte.chainetics.com. 3420 IN A 86.160.129.103
|
DNS Seeder / Node Trackers
|
|
|
movellan
|
|
February 06, 2022, 07:34:11 AM |
|
I did set up a node tracker / DNS seeder for fun, with the few IP's I found on the thread; but so far it has not found any novel nodes, it just gives back the hard coded IP from this thread: 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.
|
|
|
|
dbkeys
|
|
February 06, 2022, 11:05:52 AM Last edit: February 07, 2022, 02:42:59 AM by dbkeys |
|
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 ): // 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:
// 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
|
DNS Seeder / Node Trackers
|
|
|
movellan
|
|
February 07, 2022, 01:01:27 PM |
|
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
|
|
February 09, 2022, 12:35:23 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?
|
DNS Seeder / Node Trackers
|
|
|
movellan
|
|
February 10, 2022, 06:04:07 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
|
|
February 11, 2022, 02:03:32 PM |
|
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.
|
DNS Seeder / Node Trackers
|
|
|
|
movellan
|
|
June 01, 2023, 05:17:52 AM |
|
Hey Prof, are you mining again?
|
|
|
|
movellan
|
|
February 18, 2024, 07: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.
|
|
|
|
cpu6502
Jr. Member
Offline
Activity: 68
Merit: 1
|
|
May 01, 2024, 10:48:45 PM |
|
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/bytecoinYou 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
|
|
May 02, 2024, 07:16:46 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/bytecoinYou 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
Offline
Activity: 68
Merit: 1
|
|
May 02, 2024, 08:23:58 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
|
|
|
|
cpu6502
Jr. Member
Offline
Activity: 68
Merit: 1
|
|
May 02, 2024, 08:30:27 AM |
|
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
Offline
Activity: 68
Merit: 1
|
|
May 02, 2024, 10:54:51 PM |
|
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
Offline
Activity: 68
Merit: 1
|
|
May 07, 2024, 09:34:52 PM |
|
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: 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.
|
|
|
|
|