Prof, appreciate all the hard work you are putting into BTE, but I am dead set against any fork. Ahmed Bodi tried to go that that route so he could gain control of mining. Please explain further. TIA.
Topic: [BTE] The Bytecoin Information Thread - page 20. (Read 80094 times)
I have the opinion that 3 factors should go into the difficulty adjustment.
This opinion is captured in new technology I am calling Hard Turtle.
1. The long term mining rate of the coin.
3. The time since MedianPrevTime.
4. The new difficulty will be the cube root of difficulty_0 * difficulty_1 * difficulty_2.
5. These changes will dovetail very nicely with a distributed mining pool.
6. The old client will work with these changes for a few Intervals (epochs of 2016 blocks) but as the difficulty starts to steady out, the nBits numbers will eventually differ and cause a hard fork.
7. I am making the hard fork stronger, and repairing the entire blockchain.
8. It turns out, I can include a coinbase block for a bitcoin block as well, while I am doing the repair. Go to the survey a few postings above, and include any bitcoin address that you have been paid to in a coinbase block :-).
This opinion is captured in new technology I am calling Hard Turtle.
1. The long term mining rate of the coin.
- 600 sec / block since genesis
- adjust the difficulty_0 according to this factor
3. The time since MedianPrevTime.
- This should also be 600 sec/block.
- The value of those difficulty increases (will be) in a calculated table, and called difficulty_2.
- The actual behavior is described very well by a Poisson distribution. See the link several posts above.
- This can be control without an audit trail by changing the target hash reported in getminingtemplate
- The value of those difficulty increases (will be) in a calculated table, and called difficulty_2.
4. The new difficulty will be the cube root of difficulty_0 * difficulty_1 * difficulty_2.
- This is easy to calculate using nBits.
- After calculation, it will be clipped to a factor of 4x change, as is the current practice.
5. These changes will dovetail very nicely with a distributed mining pool.
- The difficulty items are nearing the end of development and testing.
- The mining pool has some development work.
6. The old client will work with these changes for a few Intervals (epochs of 2016 blocks) but as the difficulty starts to steady out, the nBits numbers will eventually differ and cause a hard fork.
7. I am making the hard fork stronger, and repairing the entire blockchain.
- This will result in the same transactions as before, but a blockchain with a difficulty near 1.
- It will take fewer hashes to mine 58,000 blocks at difficulty 1 than 300 blocks at difficulty 1,000,000.
- No data will be lost.
- Timestamps will be very similar.
- It took a devil of a long time to work out the logic of mining blocs nunc pro tunc.
- The blockchain repair will occur with a client that also supports the mining pool. Alternate blocks will generate new rewards, so it will be earn as you repair.
8. It turns out, I can include a coinbase block for a bitcoin block as well, while I am doing the repair. Go to the survey a few postings above, and include any bitcoin address that you have been paid to in a coinbase block :-).
This coins is 5 years old!
Code:
|_| /| |_)|_)\_/
| | /-| | | /
_ _ ___ _
|_) | |_) | |_|| \ /| \_/
|_) | | \ | | ||_/ /-| /
.--------.
.: : : :___`.
.'!!::::: \\_\ `.
: . /%O!!::::::::\\_\. \
[""]/%%O!!::::::::: : . \
| |%%OO!!::::::::::: : . |
| |%%OO!!::::::::::::: :|
| |%%OO!!!::::::::::::: :|
: .'--`.%%OO!!!:::::::::::: :|
: .: /`.__.'\%%OO!!!::::::::::::/
: . / \%OO!!!!::::::::::/
,-'``'-. ; ;%%OO!!!!!!:::::'
|`-..-'| | ,--. |`%%%OO!!!!!!:'
| . :| |_.','`.`._| `%%%OO!%%'
| . : | |--' `--| `%%%%'
|`-..-'| || | | | | /__\`-.
\::::::/ ||)|/|)|)|\| /
---------`::::'--|._ ~**~ _.|----------( -----------------------
)( | `-..-' | \ ______
)( | |,--. ____/ / /\\ ,-._.-'
,-')('-. | |\`;/ .-()___ : |`.!,-'`'/`-._
( ' ` )`-._ _.-'|;,| `-, \_\__\`,-'>-.,-._
`-....-' ```` `--' `-._ (`- `-._`-. hjw
| | /-| | | /
_ _ ___ _
|_) | |_) | |_|| \ /| \_/
|_) | | \ | | ||_/ /-| /
.--------.
.: : : :___`.
.'!!::::: \\_\ `.
: . /%O!!::::::::\\_\. \
[""]/%%O!!::::::::: : . \
| |%%OO!!::::::::::: : . |
| |%%OO!!::::::::::::: :|
| |%%OO!!!::::::::::::: :|
: .'--`.%%OO!!!:::::::::::: :|
: .: /`.__.'\%%OO!!!::::::::::::/
: . / \%OO!!!!::::::::::/
,-'``'-. ; ;%%OO!!!!!!:::::'
|`-..-'| | ,--. |`%%%OO!!!!!!:'
| . :| |_.','`.`._| `%%%OO!%%'
| . : | |--' `--| `%%%%'
|`-..-'| || | | | | /__\`-.
\::::::/ ||)|/|)|)|\| /
---------`::::'--|._ ~**~ _.|----------( -----------------------
)( | `-..-' | \ ______
)( | |,--. ____/ / /\\ ,-._.-'
,-')('-. | |\`;/ .-()___ : |`.!,-'`'/`-._
( ' ` )`-._ _.-'|;,| `-, \_\__\`,-'>-.,-._
`-....-' ```` `--' `-._ (`- `-._`-. hjw
{"block":"58137"} 
Many blocks found in the past few hours.
{"block":"58135"}
{"block":"58135"}
Building a blockchain API for this coin.
You can test here.
http://34.233.28.56:3000/getmininginfo
http://34.233.28.56:3000/getnewaddress
You can test here.
http://34.233.28.56:3000/getmininginfo
http://34.233.28.56:3000/getnewaddress
Add this line in your bytecoin.conf file
addnode=52.205.185.242:6333
Also my mining info shows this:
addnode=52.205.185.242:6333
Also my mining info shows this:
I can put you in the dns entry at seed.bte.vima.austin.tx.us if you give permission.
edited 2018-03-29
I decided your post was permission enough. I have added your address to the
DNS entry. It is live and tested with dig.
So, I recommend using the following line in your bytecoin.conf or the command line.
Code:
seednode=seed.bte.vima.austin.tx.us
Add this line in your bytecoin.conf file
addnode=52.205.185.242:6333
Also my mining info shows this:
addnode=52.205.185.242:6333
Also my mining info shows this:
Code:
{
"version" : 80101,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 58128,
"connections" : 3,
"proxy" : "",
"difficulty" : 1056741.21450361,
"testnet" : false,
"keypoololdest" : 1514085788,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
"version" : 80101,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 58128,
"connections" : 3,
"proxy" : "",
"difficulty" : 1056741.21450361,
"testnet" : false,
"keypoololdest" : 1514085788,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
Prof,
Looks like someone found a new block, 58127. I'm still showing a connection to only your node. No others detected.
Looks like someone found a new block, 58127. I'm still showing a connection to only your node. No others detected.
Prof,
Not sure what files you want to move but in Windoze are located at:
C:\Users\User\AppData\Roaming\Bytecoin
Have been deleting debug.log and peers.dat before each time I try a new config. Added addresses first using console "onetry" and next adding to Bytecoin.conf. Your node is still the only one standing. Attempted nodes have log entry such as:
2018-03-26 06:07:08 trying connection xxx.xxx.xxx.xxx:6333 lastseen=395012.3hrs
2018-03-26 06:07:13 connection timeout
HTH. Thanks.
In Linux, you might start an investigation session with
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
[/quote]
I'll look for some. Meanwhile, manually move those files out of the directory that they are in.
Someone who can check a windows environment, please post the details of where that directory is located.
[/quote]
Not sure what files you want to move but in Windoze are located at:
C:\Users\User\AppData\Roaming\Bytecoin
Have been deleting debug.log and peers.dat before each time I try a new config. Added addresses first using console "onetry" and next adding to Bytecoin.conf. Your node is still the only one standing. Attempted nodes have log entry such as:
2018-03-26 06:07:08 trying connection xxx.xxx.xxx.xxx:6333 lastseen=395012.3hrs
2018-03-26 06:07:13 connection timeout
HTH. Thanks.
In Linux, you might start an investigation session with
Code:
export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
I'll look for some. Meanwhile, manually move those files out of the directory that they are in.
Someone who can check a windows environment, please post the details of where that directory is located.
[/quote]
Prof,
Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.
In Linux, you might start an investigation session with
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.
In Linux, you might start an investigation session with
Code:
export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
I'll look for some. Meanwhile, manually move those files out of the directory that they are in.
Someone who can check a windows environment, please post the details of where that directory is located.
Prof,
Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.
In Linux, you might start an investigation session with
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.
In Linux, you might start an investigation session with
Code:
export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
Prof,
Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.
What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.
Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.
What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.
In Linux, you might start an investigation session with
Code:
export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &
Then, it should create a new peers.dat that only has the peers it gets from my node.
Then you can search debug.log for
"trying connection"
and that should show the nodes it is trying to connect to.
Yes, Bitcoin is best. I tried BTE back when it started because it was a clone of Bitcoin. Mined some when BTC network difficulty went too high. Would like to get see it going again.
Personally, I have yet to see a change that any alt-coins have made that I can unequivocally regard to be an improvement over Bitcoin at this point (although some of the changes may prove to be so, eventually). So to me, if I want an additional currency, the best choice is an identical fork of Bitcoin.
Personally, I have yet to see a change that any alt-coins have made that I can unequivocally regard to be an improvement over Bitcoin at this point (although some of the changes may prove to be so, eventually). So to me, if I want an additional currency, the best choice is an identical fork of Bitcoin.
Prof,
Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.
What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.
My electricity was off for a few hours today. When I booted back up just now, some new nodes connected, and my block count went from 58122 to 58126. However, there was a re-organization back 16 blocks, and the newest block now is back to Sat Aug 27 01:26:49 2016 instead of last week. Apparently the nodes have been fragmented for some time.
I think it is important that everyone try to accept connections from each other as well as reach out to each other. If I get hit by a truck or something and no one else allows each other to connect, the network is still vulnerable.
Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.
What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.
Prof,
My electricity was off for a few hours today. When I booted back up just now, some new nodes connected, and my block count went from 58122 to 58126. However, there was a re-organization back 16 blocks, and the newest block now is back to Sat Aug 27 01:26:49 2016 instead of last week. Apparently the nodes have been fragmented for some time.
I think it is important that everyone try to accept connections from each other as well as reach out to each other. If I get hit by a truck or something and no one else allows each other to connect, the network is still vulnerable.
Prof,
Any idea why my block height is well above the one you show? How do we get more nodesup?
Any idea why my block height is well above the one you show? How do we get more nodesup?
My electricity was off for a few hours today. When I booted back up just now, some new nodes connected, and my block count went from 58122 to 58126. However, there was a re-organization back 16 blocks, and the newest block now is back to Sat Aug 27 01:26:49 2016 instead of last week. Apparently the nodes have been fragmented for some time.
I think it is important that everyone try to accept connections from each other as well as reach out to each other. If I get hit by a truck or something and no one else allows each other to connect, the network is still vulnerable.
Prof,
Yes, it must be my node as it has last block as 58126.
getblockhash 58122 returns:
0000000000000f92d9816911e63b3dc6e0186c07bda22a926e86a8d4050fec05
get blockinfo reurns:
?
[
{
"addr" : "bte.vima.austin.tx.us",
"services" : "00000001",
"lastsend" : 1521883449,
"lastrecv" : 1521883449,
"conntime" : 1521883448,
"version" : 70001,
"subver" : "/Satoshi:0.8.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 58122,
"banscore" : 0
}
]
Any idea why my block height is well above the one you show? How do we get more nodesup?
Yes, it must be my node as it has last block as 58126.
getblockhash 58122 returns:
0000000000000f92d9816911e63b3dc6e0186c07bda22a926e86a8d4050fec05
get blockinfo reurns:
?
[
{
"addr" : "bte.vima.austin.tx.us",
"services" : "00000001",
"lastsend" : 1521883449,
"lastrecv" : 1521883449,
"conntime" : 1521883448,
"version" : 70001,
"subver" : "/Satoshi:0.8.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 58122,
"banscore" : 0
}
]
Any idea why my block height is well above the one you show? How do we get more nodesup?
There are IP addresses that show up in my debug.log that my node can't connect back to. I think the software automatically shares all the IPs that it learns about, so that the blocks get distributed and are safe. I think we need more active nodes and connections at the moment.
So, some commands that you might want to AVOID except under special circumstances are
listen=0
connect=
noconnect
connect=0
So, some commands that you might want to AVOID except under special circumstances are
listen=0
connect=
noconnect
connect=0
There are IP addresses that show up in my debug.log that my node can't connect back to. I think the software automatically shares all the IPs that it learns about, so that the blocks get distributed and are safe. I think we need more active nodes and connections at the moment.
So, some commands that you might want to AVOID except under special circumstances are
listen=0
connect=
noconnect
connect=0
So, some commands that you might want to AVOID except under special circumstances are
listen=0
connect=
noconnect
connect=0
Jump to: