 Show Posts
|
|
Pages: [1]
|
|
I see mentioned zPIV v1 and v2.
How do I know if my zPIV balance is v1 or v2??
|
|
|
|
|
I am still trying to determine the profitability of CPU-farming this coin...
Nobody could give a formula from hashrate & difficulty? Thanks in advance!
|
|
|
|
need some testers to test the pool.
stratum+tcp://stratum.minertopia.org:7000 -u your vrm address -p c=VRM
Getting authentication failures |
|
|
|
Segwit works with mining hardware. Any claims you see about PoW changes, are made by lunatics who are high on drugs. Ignore them. You intend to support Segwit2x proposal, right? |
|
|
|
Indeed, after a long period of high difficulty, unjustifiably high at least with respect to the price, we gradually returned to levels I'm comfortable with. Enough so to divert 100% of my cpu mining back to bip. Let's see how long it lasts.
Just gotta hope people are willing to pay decent prices for the new coins coming into circulation. little-known secret: BipCoin is one of the most profitable coins to mine (and has been for months). And the difficulty is WAY lower then most profitable coins, so open to people with less mining power: http://whattomine.com/And BipCoin is usually the most profitable CryptoNote coin to mine. Profitable, but are you really able to sell your coins with such low daily volumes, without crashing the price? |
|
|
|
|
Hello,
looking at the result of "netstat" after leaving the node run for several days now, I notice that I have many connections with 94.113.207.67
Looks like a bug in the communication protocol? I would imagine a normal behavior would be to multiplex communications in 1 or 2 TCP streams?
TCP 10.97.2.9:62086 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62241 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62242 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62244 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62256 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62259 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62262 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62263 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62265 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62267 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62268 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62274 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62278 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62292 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62293 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62294 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62295 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62296 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62350 58.173.246.16:8333 ESTABLISHED 4616
TCP 10.97.2.9:62363 162.243.250.176:2829 ESTABLISHED 4988
TCP 10.97.2.9:62434 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62437 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62438 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62440 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62445 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62457 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62463 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62466 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62475 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62479 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62500 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62548 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62550 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62551 94.113.207.67:2829 ESTABLISHED 4988
TCP 10.97.2.9:62564 94.113.207.67:2829 ESTABLISHED 4988
|
|
|
|
Well first, is there a 'clean' shutdown procedure to stop node.exe (Ctrl-C exception is catched) other than "kill -9" or equivalent? I upgraded to the latest version, restarted everything and waited a while until the "Block Height" would stabilize (now 10299). However since I restarted everything, I am missing a 25-bismuth reward (I had 3 before the upgrade, and now only have 2). Is it because of the upgrade itself? -Zorgn |
|
|
|
|
Hello,
I noticed this strange behavior: when you keep pressing the "Refresh" button on the GUI, the last transaction sometimes disappear (if you press refresh enough it will eventually reappear)
Just FYI...
|
|
|
|
Upgraded mine. Just noticed: I did a transaction of 0.102, and it shows on the GUI as 0.1 only, so maybe you should not be rounding the display...? |
|
|
|
Testnet transaction spammer is not running, at least not mine
That explains why my miner was no longer doing anything I guess! |
|
|
|
|
Just discovered this gem, really looks interesting and different.
I really encourage the author not to rush out the main net, and test, test and test again first :-)
It's so painful to discover weaknesses and have to hard fork when there is some real money at stake...
Zorgn
bd19c964e3208f0b28685f52d6fc6ab46aea108f1500c55baaec5da3 (feel free to send fake bismuths there! ^^)
|
|
|
|
Wrong command. Try "get_mining_queue" If you are in the queue and don't get a block reward when you get to the front of the queue, that means you are either missing a witness= line in your config, or you have and issue with keys. The miner= line has to include your active key and, if different, your witness signing key (use get_witness to check) needs to be in a private-key= line. But I stayed in queue at number 108,107,106,103,107,108 for about 12-14 hours ... Is that normal? I have the exact same problem..... :-( |
|
|
|
|
