miner.rocks
Jr. Member
Offline
Activity: 181
Merit: 2
|
|
April 19, 2018, 03:26:18 PM |
|
Hello, fellow miners! Pool itns.miner.rocks (cn-v7)updated to v2 mainnet and in sync with intensecoin.com/pool Features:- email notifications of workers down - stats and hashrate chart per worker - PPLNS reward scheme - payment id supported (integrated address support will be added in a day) - adjustable payment threshold - every port supports secure SSL/TLS connection as well as insecure one - port 80 available for firewalled miners - static diff supported, see static diff calculator- multiple daemons, to prevent downtime in case of daemon stuck - height checks, to prevent mining on forked chain - sample configs for cn-v7 supported mining apps PPLNS fee: 0.1% Location: EU Welcome & Lucky Mining!
|
https://miner.rocks pplns cryptonote pools with email alerts and workers stats
|
|
|
miner.rocks
Jr. Member
Offline
Activity: 181
Merit: 2
|
|
April 19, 2018, 03:57:58 PM |
|
Strange, but itns.miner.rocks has network difficulty, different from intensecoin.com/pool, but the last block header hash is the same. We use json_rpc to check daemon network difficulty, and it seems we show correct difficulty at pool site: curl -s --data-binary '{"jsonrpc": "2.0","id": "test","method": "getlastblockheader","params": {}}' -H 'content-type:text/plain;' http://127.0.0.1:48782/json_rpc
And the result is { "id": "test", "jsonrpc": "2.0", "result": { "block_header": { "block_size": 103, "depth": 0, "difficulty": 56451687, "hash": "6ea8bb1d91fc9d6ccc497c45feb46da5df2c8b67e8b5940897ee82df99829561", "height": 166443, "major_version": 4, "minor_version": 4, "nonce": 150005, "num_txes": 0, "orphan_status": false, "prev_hash": "98e0c7336f74ecbf7707ee675af78700f26e538a50c4d40c96754231027143fe", "reward": 138793780000, "timestamp": 1524152751 }, "status": "OK" } }
|
https://miner.rocks pplns cryptonote pools with email alerts and workers stats
|
|
|
jardine
|
|
April 19, 2018, 04:26:57 PM |
|
Is it possible migrate that way:
1) Sync my old 1.4.1 wallet 2) Download new monero-rebase wallet 3) Create new monero-rebase wallet 4) Send my balance from 1.4.1 to new wallet
?
|
|
|
|
miner.rocks
Jr. Member
Offline
Activity: 181
Merit: 2
|
|
April 19, 2018, 04:34:00 PM |
|
Is it possible migrate that way:
1) Sync my old 1.4.1 wallet ...
Only if you are lucky to sync with 1.4.1 daemon. It can stuck somewhere.
|
https://miner.rocks pplns cryptonote pools with email alerts and workers stats
|
|
|
ThePigwee
Member
Offline
Activity: 181
Merit: 46
Lethean COO
|
|
April 19, 2018, 04:34:42 PM |
|
Is it possible migrate that way:
1) Sync my old 1.4.1 wallet 2) Download new monero-rebase wallet 3) Create new monero-rebase wallet 4) Send my balance from 1.4.1 to new wallet
?
No, if you send from your old wallet to the rebase wallet, after the roll back those ITNS will be back in your wallet.
|
|
|
|
MagicSmoker
|
|
April 19, 2018, 05:26:34 PM |
|
The reddit guide is still 100% valid
The blockchain should automatically reorganize. It will definitely happen when the v4 chain exceeds the v3 chain. If your v3 (pre-fork) chain was synced to be longer than the current v4 chain, and you're having troubles syncing the current v4 chain, use `intense-blockchain-import --pop-blocks 7500` to manually discard 7500 blocks from your chain.
Yep, I'm seeing the daemon report being ever more behind in blocks at around the 7460 mark so I'll try the blockchain import command. EDIT - how long does this command usually run for, and how do you know it is done? EDIT 2 - well, I got an answer to the above question - it terminated "after throwing an instance of 'boost::exception_detail::clone_imp<boost..." something or other which is way too tedious to type because I run wallets on an isolated laptop, not the desktop I am typing this post on. So I left the daemon up after discarding the last 7500 blocks as instructed earlier and it did, appear, to start from 7500 blocks earlier but the daemon once again seems to be stuck at block 166391 which may or may not be okay. I would like to resume mining, but I would also very much like to ensure coins will make to it my wallet.
|
|
|
|
YaStaer
Member
Offline
Activity: 137
Merit: 10
|
|
April 19, 2018, 06:53:18 PM |
|
For normal sync daemon, run with parameters: intensecoind.exe --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 5.249.27.162:48772 and wait...
|
|
|
|
J4CKT
Newbie
Offline
Activity: 30
Merit: 0
|
|
April 19, 2018, 07:02:51 PM |
|
If anyone else gets stuck as I did when watching the video instructions to generate a new wallet but at the part where he instructs you to download the CLI - the github link on the website does not lead to it . CLI to generate new wallet is located here: https://github.com/valiant1x/intensecoin/releases/tag/v2.0.0After generating the new wallet he talks about downloading the GUI wallet and that is nowhere to be seen from the website Github link either, but its located here: https://github.com/valiant1x/intensecoinwallet/releasesThis would have saved a lot of time if the the github link on the Intense website was upto date.
|
|
|
|
condour_btc
Newbie
Offline
Activity: 1
Merit: 0
|
|
April 19, 2018, 07:05:53 PM |
|
I installed intensecoin wallet v 1.4.2 ,when I closed it and re open again , this error occurred : blockchain load error !!
|
|
|
|
|
Boriss
|
|
April 19, 2018, 07:36:26 PM |
|
I have currently wallet version v1.2-alpha - First version that become available, can I install 1.4.2 or I must first jump to some in between version before I run 1.4.2 with my old backup wallet?
|
|
|
|
CryptoPlay
Jr. Member
Offline
Activity: 202
Merit: 2
|
|
April 19, 2018, 08:23:02 PM Last edit: April 19, 2018, 08:36:23 PM by CryptoPlay |
|
Hey bro, Network is out of sync.... every single pool mining its own network with different numbers. deal with it! Why are you all mining in the official pool? look at the message: ** NOTE ** This pool is still experimenting with updating to the latest fork. Payments for blocks may be broken, mine at your own risk! Go to https://intense.hashvault.pro/
|
https://signature.statseb.fr/sig-2065.png
|
|
|
whotheff
|
|
April 19, 2018, 09:37:10 PM |
|
can someone help relocating the wallet Database to another drive? I hate it when everything tries to overload my C: drive!
|
|
|
|
MagicSmoker
|
|
April 19, 2018, 10:06:13 PM |
|
It looks like the network is totally fubar - no block found on the official pool in over an hour and the hashvault pool also reporting effort on the current block exceeding 1300%. Well, we were warned to mine at our own risk... Also, the instructions I was given earlier to use the --add-priority-node switches to sync the daemon didn't work; I had to use --add-exclusive-node instead, as reported by @YaStaer. Once synced, the balance from my 1.4.2 wallet showed up, but not the most recent mining payments from today. So, my recommendation - worth price paid - is to stop mining until things get well and truly sorted out.
|
|
|
|
valiant1
Full Member
Offline
Activity: 219
Merit: 121
Lethean Developer
|
|
April 20, 2018, 01:43:51 AM |
|
The daemon exploded when it hit block 167k. The official pool was rolled back 400 blocks and is mining again. I'll try to update our Discord announcement post as other pool owners get their pools updated to fix the broken daemons, but in the meantime, the only pool that you can mine is http://intensecoin.com/pool . For more information, see https://github.com/valiant1x/intensecoin/issues/67#issuecomment-382936780It looks like the network is totally fubar - no block found on the official pool in over an hour and the hashvault pool also reporting effort on the current block exceeding 1300%. Well, we were warned to mine at our own risk... Also, the instructions I was given earlier to use the --add-priority-node switches to sync the daemon didn't work; I had to use --add-exclusive-node instead, as reported by @YaStaer. Once synced, the balance from my 1.4.2 wallet showed up, but not the most recent mining payments from today. So, my recommendation - worth price paid - is to stop mining until things get well and truly sorted out. Apologies for the headaches, Magic. Thanks for your patience.
|
|
|
|
fadle_aja
Newbie
Offline
Activity: 12
Merit: 0
|
|
April 20, 2018, 02:02:07 AM |
|
all pool down ?
|
|
|
|
vikec1989
Jr. Member
Offline
Activity: 129
Merit: 5
|
|
April 20, 2018, 05:42:17 AM |
|
It's all alright with 2.0 wallet. I have had problem, but when it finished sync, it was all fine, all coins are transfered from 1.4.1 to 2.0 without problem. Only i dont know what will be with my 1000 coins that i sent from 1.4.1 to 1.5 wallet in that famous dates when asics done the shit on pools Are those 1000 gona be transfered back to 1.4.1 wallet? If it will, how do i send it to 2.0 wallet, if i previosly done transfer with majority of coins with guide on yt? I thnik that i lost forever those 1000 coins :/
|
|
|
|
Ayers
Legendary
Offline
Activity: 2716
Merit: 1024
Vave.com - Crypto Casino
|
|
April 20, 2018, 05:43:52 AM |
|
so how to uograde to 2.0 wallet, and when gui version?
|
|
|
|
korm
Member
Offline
Activity: 280
Merit: 10
|
|
April 20, 2018, 05:47:00 AM |
|
The daemon exploded when it hit block 167k. The official pool was rolled back 400 blocks and is mining again. I'll try to update our Discord announcement post as other pool owners get their pools updated to fix the broken daemons, but in the meantime, the only pool that you can mine is http://intensecoin.com/pool . For more information, see https://github.com/valiant1x/intensecoin/issues/67#issuecomment-382936780It looks like the network is totally fubar - no block found on the official pool in over an hour and the hashvault pool also reporting effort on the current block exceeding 1300%. Well, we were warned to mine at our own risk... Also, the instructions I was given earlier to use the --add-priority-node switches to sync the daemon didn't work; I had to use --add-exclusive-node instead, as reported by @YaStaer. Once synced, the balance from my 1.4.2 wallet showed up, but not the most recent mining payments from today. So, my recommendation - worth price paid - is to stop mining until things get well and truly sorted out. Apologies for the headaches, Magic. Thanks for your patience. Give for downloading the archive with the new BC. Why this nightmare with synchronization. Nobody really can synchronize.
|
|
|
|
|
|