Topic: Bitmark - page 47. (Read 622245 times)

I am looking for a pool and an exchange. Can anyone help?

any working markets
Poloniex Bitmark: "Temporarily Disabled"

Newborn POOL
http://scrypt.ispace.co.uk/coindetails/?coin=btm

Still no block

not sure if there is anymore since there seems to be a malicious miner on the chain causing all the other pools to orphan their blocks.

i still want to find one pool
for mining


any pool?
working???

Worked perfectly, thanks a bunch.

Was a very exciting post, I'm disappointing to read how many problems there have been with this coin it looked very promising, it shows you you cant trust a good pitch you need to wait and see results

how can i start bitmark mining. i am new in this please guide me. i buy gridseed machine's. how can i use them to mine BTM?

If you have a "connect=xxx.yyy.zzz.kkk" statement somewhere in the .conf file, and the node is not active, then the addnode statements won't have any effect.

Here's a fresh list of nodes, active now:

coins@frank:~/.zmark$ btm getpeerinfo | grep addr\"
        "addr" : "204.68.122.11:9265",
        "addr" : "198.205.118.181:60204",
        "addr" : "[2001:4060:4419:1:4030:b3ff:fe67:bb36]:9265",
        "addr" : "45.33.65.161:34296",
        "addr" : "139.59.160.118:52779",
        "addr" : "192.124.224.254:54898",
        "addr" : "157.161.128.63:9265",
        "addr" : "[2600:3c03::f03c:91ff:fef1:60bb]:9265",
        "addr" : "204.68.122.18:46986",
        "addr" : "5.101.96.124:14001",
        "addr" : "[2602:ff68:0:1:2bd:27ff:feb0:aef8]:9265",
        "addr" : "5.189.144.97:41495",
        "addr" : "204.68.122.7:56216",
        "addr" : "91.134.233.254:49653",
        "addr" : "146.0.32.101:60941",
        "addr" : "184.178.119.36:9265",
        "addr" : "85.24.169.215:9265",
        "addr" : "24.128.149.134:59460",
        "addr" : "192.99.62.23:37819",
        "addr" : "103.253.43.162:35750",
        "addr" : "98.115.147.74:46877",
        "addr" : "123.56.194.66:37098",
        "addr" : "121.75.85.56:62649",
        "addr" : "77.67.46.89:35675",
        "addr" : "72.220.127.239:51776",
        "addr" : "123.57.15.153:9265",
        "addr" : "182.92.68.127:56797",
        "addr" : "198.48.134.7:56654",
        "addr" : "198.48.134.7:56894",
coins@frank:~/.zmark$ d
1470101538 Tue Aug 2 01:32:18 UTC 2016
coins@frank:~/.zmark$

I am not synching either, no connections. I added these nodes to bitmark.conf, and still nothing. Using win7, and wallet from link in OP(0.9.4). I'm sure the problem is something I'm forgetting, but I have no idea what.... any suggestions?

Any working pools?

do u want a portuguese translation?

pm me if u need this

cya

This is a list of peers on my node. You can add them to your bitmark.conf file by adding these lines to it:

addnode=45.33.65.161
addnode=123.57.15.153
addnode=204.68.122.11
addnode=139.59.160.118
addnode=123.56.194.66
addnode=91.134.233.254
addnode=192.99.62.23
addnode=157.161.128.63
addnode=146.0.32.101
addnode=184.178.119.36
addnode=98.115.147.74
addnode=95.46.98.50

i can not sync the wallet why??

Wallets are working fine. Lot of orphans here too, though. This just tells me someone is mining it strongly to accumulate a bunch.

I tried again: 20GHs, 15 minutes - 8 orphan blocks..  

any working wallet??

any working poollllll

right.. and the attacker seems to always use 6 different ( new ) adresses, so it will be hard to detect / ban .. clever!

so do we have any community solution to this? somebody could implement a timestamping like in goldcoin.. and then we would have to hardfork,.
not really useful for such dead coin.. so we porobably just let it die..

nevertheless, i am exited about the next pump and dump! ( what else should one do with collected coins!? )

As said, I've seen this before and due to having hours and days of no mining at all (stuck on high diff/low price) BTM is even better suited for mining a private chain and releasing blocks as needed when the public chain catches up.

If it follows the other coins where I have witnessed this "problem", then no honest miner will ever see a matured block anymore.
The wallet error seems to occure whenever a bunch of blocks are released from the selfish miner and persists as long as a majority of nodes hasn't followed it completely and therefor is on different blockheights for some time. When I check in my debug.log, I see that often a dozen of blocks come in within seconds and trigger that error. While two blocks in a row happen to every halfway lucky miner from time to time, something like a dozen or so in a row (few seconds) happens rather seldom (actually never).

I suspect other coins with a noteable marketcap and a diff in the hundreds will follow this path.