Multipool
Topic: [*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4] - page 155. (Read 379550 times)
Do we have miners with own equipment here?
As I was a bit late to the 8bit adventure (I was attracted by masternoding like a month ago), and I don't see it listed anywhere obvious, what algorithm are we using, scrypt?
I've also got a so-so GPU (just one), and I CPU mine XMG (it's algorithm is rigged for CPU mining only, which I LOVE in a mined coin, it keeps things from being dominated by folks who can drop $10k USD on a rig)
At any rate, I've flirted with the idea of building a pool, and I've got a couple of gridseed dualminers that I think still work.
What are you looking to accomplish?
Busy this days, will try to be up to date within the next days
Do we have miners with own equipment here?
ANN link is fine.
i can not download the wallet.
Is there something wrong?
https://www.dropbox.com/s/c3dx56aki99c83f/8bit-qt-2.1-win.zip?dl=0
Is there something wrong?
https://www.dropbox.com/s/c3dx56aki99c83f/8bit-qt-2.1-win.zip?dl=0
Price is looking good nobody dumping 
Maybe we can see 100K as new floor
Maybe we can see 100K as new floor
To be honest...
I would rather see panic sell instead of this market clinch. I still have not shown anything absolutely brilliant so, hey people, don't you think you should at least put some reasonable ASKs?
I know most of us paid more than 100k sat for a single coin, but hey, we all either stake or install masternodes, I am not saying you should sell anything below buy-price, just put some of your extra income to orderbooks to bring liquidity to the market. Grasp all, lose all. And don't tell me - you first. I owe you noting.
Some people send me with ideas like 'hey man if it's takeover and restart why don't you simply disappear for a week or claim you are not sure that you will stay here because of your personal issues just to restore liquidity on bittrex'. Stop this. We must be reasonable, we must be sensible. Don't send me such ideas as, besides I think it's pretty pity, it looks like a provocation.
Weeks ago I said I am not intersted in P&D here, so don't expect me being happy of market value growth without reason. Just because I believe it's all about speculation it does not mean I love speculation. Yes, I am happy that people believe in this coin, but my goal is to deliver success, not to see success in people belief.
I get your angle.. but also the MN and staking takes resources energy etc..
I really think people are not ready to sell around 50K.
I agree we need natural growth based on accomplishments made by the dev/team and/or community
Price is looking good nobody dumping
Maybe we can see 100K as new floor
Maybe we can see 100K as new floor
To be honest...
I would rather see panic sell instead of this market clinch. I still have not shown anything absolutely brilliant so, hey people, don't you think you should at least put some reasonable ASKs?
I know most of us paid more than 100k sat for a single coin, but hey, we all either stake or install masternodes, I am not saying you should sell anything below buy-price, just put some of your extra income to orderbooks to bring liquidity to the market. Grasp all, lose all. And don't tell me - you first. I owe you noting.
Some people send me with ideas like 'hey man if it's takeover and restart why don't you simply disappear for a week or claim you are not sure that you will stay here because of your personal issues just to restore liquidity on bittrex'. Stop this. We must be reasonable, we must be sensible. Don't send me such ideas as, besides I think it's pretty pity, it looks like a provocation.
Weeks ago I said I am not intersted in P&D here, so don't expect me being happy of market value growth without reason. Just because I believe it's all about speculation it does not mean I love speculation. Yes, I am happy that people believe in this coin, but my goal is to deliver success, not to see success in people belief.
N270 is 32-bit CPU so it's obvious your 8bitd is 32-bit.
My bet is that VM is also 32-bit. Am I right? I am trying to verify that my observations are correct.
Official Windows binary is 32-bit one, although 200M is stil not bad, I bet 64-bit version would consume even more.
My bet is that VM is also 32-bit. Am I right? I am trying to verify that my observations are correct.
Official Windows binary is 32-bit one, although 200M is stil not bad, I bet 64-bit version would consume even more.
OK... here's the breakdown. (not that I was asking anything, just answering your question)
1 masternode running on Atom N270, 32bit crunchbang++ Linux, wallet compiled from source on that box, 100'ish MB ram usage
5 masternodes running on a single VM (virtualbox), hosted on Intel Core2 Duo, 64bit Ubuntu 14.04 server Linux (both host and guest OSs), wallet compiled from source on that box, 130'ish MB ram usage per 8bit instance.
1 staking wallet running on Intel i5, 64bit Windows8, your 32bit binary from the 8bit website, 200'ish MB ram usage.
1 other wallet that I'll tell you all what it's for soon
, not staking OR masternode, on VPS (KVM based VM), Xeon CPU, 64bit Ubuntu 14.04 server, wallet compiled from source on that box, 130'ish MB ram usage.Sooooo, that's the 8bit stuff I'm running in a nutshell.
Price is looking good nobody dumping
Maybe we can see 100K as new floor
Maybe we can see 100K as new floor
N270 is 32-bit CPU so it's obvious your 8bitd is 32-bit.
My bet is that VM is also 32-bit. Am I right? I am trying to verify that my observations are correct.
Official Windows binary is 32-bit one, although 200M is stil not bad, I bet 64-bit version would consume even more.
My bet is that VM is also 32-bit. Am I right? I am trying to verify that my observations are correct.
Official Windows binary is 32-bit one, although 200M is stil not bad, I bet 64-bit version would consume even more.
I've got one masternode running on an old netbook, 1G ram and an atom n270 processor... Granted that's all it's doing, and it's running a rather slim version of Linux, but it hasn't had any problems, and it's memory footprint is actually smallish. On average something like 100M. I've also got five masternodes running on a much more capable VM, with 2G of RAM, also Linux, and each instance eats a similar amount of memory.
Now, I've got yet another wallet running on a windows box, and that one's staking, not a masternode... THAT one eats over 200M of memory. I just chalk it up to windoze being windoze though.
Now, I've got yet another wallet running on a windows box, and that one's staking, not a masternode... THAT one eats over 200M of memory. I just chalk it up to windoze being windoze though.
Nope, this is not how it works.
8bitd is killed by OOM killer, so it does not even know that it has been killed. There's no warning before. There are signals you can intercept, analyze and shut down graceful, but not not this one. And this is how it always work, not matter if it's 8bitd or bitcoind or Xorg or vim.
What I recommend is running simple script like:
this is proof of concept, not tested.
8bitd is killed by OOM killer, so it does not even know that it has been killed. There's no warning before. There are signals you can intercept, analyze and shut down graceful, but not not this one. And this is how it always work, not matter if it's 8bitd or bitcoind or Xorg or vim.
What I recommend is running simple script like:
Code:
while 1:
pgrep 8bitd && 8bitd
sleep 1m
This also affects most PoS coins, they are memory hungry.
Anyway 1G RAM is enough to run 5-7 instances of 8bitd. I have not tested that numbers with masternodes, but for staking needs it's OK.
There are 8bit.conf parameters you tweak on lowmem boxes like par, dbcache, maxconnections, rpcthreads, maxorphanblock that may help with reducing memory usage.
Also, on lowend box I recommend 32-bit OS or at least 32-bit 8bitd on 64-bit OS.
Yes I understand it. I had also one java instance which probably was a reason for short on memory. But some crash logging would be very useful. Anyway 1G RAM is enough to run 5-7 instances of 8bitd. I have not tested that numbers with masternodes, but for staking needs it's OK.
There are 8bit.conf parameters you tweak on lowmem boxes like par, dbcache, maxconnections, rpcthreads, maxorphanblock that may help with reducing memory usage.
Also, on lowend box I recommend 32-bit OS or at least 32-bit 8bitd on 64-bit OS.
This also affects most PoS coins, they are memory hungry.
Anyway 1G RAM is enough to run 5-7 instances of 8bitd. I have not tested that numbers with masternodes, but for staking needs it's OK.
There are 8bit.conf parameters you tweak on lowmem boxes like par, dbcache, maxconnections, rpcthreads, maxorphanblock that may help with reducing memory usage.
Also, on lowend box I recommend 32-bit OS or at least 32-bit 8bitd on 64-bit OS.
Anyway 1G RAM is enough to run 5-7 instances of 8bitd. I have not tested that numbers with masternodes, but for staking needs it's OK.
There are 8bit.conf parameters you tweak on lowmem boxes like par, dbcache, maxconnections, rpcthreads, maxorphanblock that may help with reducing memory usage.
Also, on lowend box I recommend 32-bit OS or at least 32-bit 8bitd on 64-bit OS.
I've got a VPS with 1Gb RAM and 2 8bit nodes. I noticed that 8bit daemon can terminate without any notification, nothing in debug.log. I guess the problem is in low memory but you should be aware that nodes require constant monitoring at the moment.
thank you for the update. but:
Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.can you explain that please? why 1-2 days instead of weeks? slow wallets? they also can wait 2 weeks longer..
If there had been something really wrong I would have abandon ship instead of announcing update, right? So just trust me, I will reveal more details after release.Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.
thank you for the update. but:
Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.can you explain that please? why 1-2 days instead of weeks? slow wallets? they also can wait 2 weeks longer..
If there had been something really wrong I would have abandon ship instead of announcing update, right? So just trust me, I will reveal more details after release.Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.
thank you for the update. but:
Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.can you explain that please? why 1-2 days instead of weeks? slow wallets? they also can wait 2 weeks longer..
Third, I planned to make final public release next week with hardcoded hardfork 2-3 weeks later to make sure people will update without hurry. Now I see that hardfork will have to be made immediately (1-2 days) after public release.
I would like to help testing the new version.
Im not having a lot of free time this past days, but i would like to help
Im not having a lot of free time this past days, but i would like to help
Jump to: