Topic: [BTE] The Bytecoin Information Thread - page 14. (Read 80168 times)
It looks like it has possibilities except that almost half the coins are in one wallet. Most people pass on monopoly coins.
Is a block explorer going to be made available?
Okay, it would be great to get this up and running again as proof of resilience.
Technically, it is up an running now. Blocks are being processed, transactions get confirmed.
Okay, it would be great to get this up and running again as proof of resilience.
I'm down for a while. OS update taking longer than expected.
Prof, how far away are we for next difficulty adjustment?
At the current mining rate, more than a year.
Can you share your calculations?
At the rate of 2 blocks per day it looks like the retarget is sooner than "more than a year"
I grabbed some data.
Code:
block 58250, timestamp 1529219483
block 58150, timestamp 1523062269
61,572 sec / block, or 17.1 hr/block
29 * 2016 - 58250 = 214 block to retarget
214 * 17.1 = 3,660 hours to retarget
--> 152 days.
block 58150, timestamp 1523062269
61,572 sec / block, or 17.1 hr/block
29 * 2016 - 58250 = 214 block to retarget
214 * 17.1 = 3,660 hours to retarget
--> 152 days.
Now we are talking Prof! Excellent
I'm down for a while. OS update taking longer than expected.
Prof, how far away are we for next difficulty adjustment?
At the current mining rate, more than a year.
Can you share your calculations?
At the rate of 2 blocks per day it looks like the retarget is sooner than "more than a year"
I grabbed some data.
Code:
block 58250, timestamp 1529219483
block 58150, timestamp 1523062269
61,572 sec / block, or 17.1 hr/block
29 * 2016 - 58250 = 214 block to retarget
214 * 17.1 = 3,660 hours to retarget
--> 152 days.
block 58150, timestamp 1523062269
61,572 sec / block, or 17.1 hr/block
29 * 2016 - 58250 = 214 block to retarget
214 * 17.1 = 3,660 hours to retarget
--> 152 days.
I'm down for a while. OS update taking longer than expected.
Prof, how far away are we for next difficulty adjustment?
At the current mining rate, more than a year.
Can you share your calculations?
At the rate of 2 blocks per day it looks like the retarget is sooner than "more than a year"
I'm down for a while. OS update taking longer than expected.
Prof, how far away are we for next difficulty adjustment?
At the current mining rate, more than a year.
Forever turns out to be a long time. Cryptsy went belly-up 3 years ago.
Cryptsy has a BTE/BTC pair. Been waiting for my bottom bid to be filled forever Roll Eyes Grin
I downloaded android-studio into a VirtualBox guest and made my Hello World. I upgraded my Ubuntu host from 14.04 --> 16.04, upgraded the Ubuntu guest to 18.04. I made a few time consuming rookie mistakes during the upgrade.
Later, I found a miner written in Java for the android. I imported this into Google's android-studio, and it does run on my phone, using getwork with my local client. I did use rpcallowip= to allow RPC calls from the phone.
It claims to be mining at about 9.8 KH/s. My client is set up with a test-chain at difficulty 1, I have not waited to see if this delivers a block or not in my excitement to post here.
I don't think this is a serious mining application in today's environment, but it was a relevant "Hello World again" program.
This program is not very friendly when there are problems in the configuration, but still, I think it is newsworthy.
You may wish to
git clone [email protected]:a-mcintosh/bminer.git
git checkout studio
I took a break from the Hard-Turtle programming while I did all this.
Later, I found a miner written in Java for the android. I imported this into Google's android-studio, and it does run on my phone, using getwork with my local client. I did use rpcallowip=
It claims to be mining at about 9.8 KH/s. My client is set up with a test-chain at difficulty 1, I have not waited to see if this delivers a block or not in my excitement to post here.
I don't think this is a serious mining application in today's environment, but it was a relevant "Hello World again" program.
This program is not very friendly when there are problems in the configuration, but still, I think it is newsworthy.
You may wish to
git clone [email protected]:a-mcintosh/bminer.git
git checkout studio
I took a break from the Hard-Turtle programming while I did all this.
Cryptsy has a BTE/BTC pair. Been waiting for my bottom bid to be filled forever Roll Eyes Grin
If you want lower difficulties or different hashing algorithims then create your AhmedCoin and let bytecoin grow organically the way it is doing so far. I know you are mad because current difficulty is too high for your mining hardware but the protocol is on schedule to release the 21,000,000 coins in the 140 year timeframe.
I'm down for a while. OS update taking longer than expected.
Prof, how far away are we for next difficulty adjustment?
I'm down for a while. OS update taking longer than expected.
Anyone? ...
I looked at it, but not too much. I did download the android studio package, wrote hello world, and looked to see how many android bitcoin packages were on GitHub.
But all that is a distraction from getting the existing client out the door with the Hard Turtle enhancements.
Anyone? ...
I keep getting the following error:
In file included from ./port/port_posix.h:50:0, from ./port/port.h:14,
from ./db/filename.h:14,
from db/builder.cc:7:
./port/atomic_pointer.h:212:2: error: #error Please implement AtomicPointer for this platform. #error Please implement AtomicPointer for this platform.
^~~~~
Makefile:198: recipe for target 'db/builder.o' failed make[1]: *** [db/builder.o] Error 1
make[1]: Leaving directory '/root/bytecoin/src/leveldb'
makefile.unix:151: recipe for target 'leveldb/libleveldb.a' failed make: *** [leveldb/libleveldb.a] Error 2
In file included from ./port/port_posix.h:50:0, from ./port/port.h:14,
from ./db/filename.h:14,
from db/builder.cc:7:
./port/atomic_pointer.h:212:2: error: #error Please implement AtomicPointer for this platform. #error Please implement AtomicPointer for this platform.
^~~~~
Makefile:198: recipe for target 'db/builder.o' failed make[1]: *** [db/builder.o] Error 1
make[1]: Leaving directory '/root/bytecoin/src/leveldb'
makefile.unix:151: recipe for target 'leveldb/libleveldb.a' failed make: *** [leveldb/libleveldb.a] Error 2
Let me get the BTE wallet running in my Samsung Android phone. Ill paste the BTE address soon. Thank you Prof.
Can you build it for the Android?
I use TERMUX on my phone. Inside TERMUX I installed Arch Linux. Trying to build in there but leveldb is giving me trouble.
I installed TERMUX on a Samsung J7. This is an octa-core phone.
I cloned
git clone [email protected]:tpruvot/cpuminer-multi.git ~/opt/coins/cpuminer
I apt-get installed many dependencies, and added LOCAL_LDLIBS := -L/system/lib -llog
As always with Unix, there is more essential information that I have not included.
Now I have a cpuminer on my phone, and have generated a few blocks in my test environment.
AWESOME!
Can you teach us step by step with screenshots and code snippets how you did it? Also, are you BTE mining?
Wrong forum. This is Bytecoin (BTE) support.
I'm holding some BCN that I've mined. Back then when I was mining I didn't want to sell them... hell now they are at a very low price and i won't get nada for them. Do you think we can see the price go back up???
I'm holding some BCN that I've mined. Back then when I was mining I didn't want to sell them... hell now they are at a very low price and i won't get nada for them. Do you think we can see the price go back up???
Jump to: