Pages:
Author

Topic: [ANN] INTENSE COIN - Blockchain backed decentralized VPN - Hybrid PoW - page 37. (Read 235822 times)

member
Activity: 762
Merit: 35
can someone help relocating the wallet Database to another drive?
I hate it when everything tries to overload my C: drive!
jr. member
Activity: 202
Merit: 2
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/
full member
Activity: 728
Merit: 115
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?
member
Activity: 426
Merit: 11
newbie
Activity: 1
Merit: 0
I installed  intensecoin wallet v 1.4.2 ,when I closed it and re open again  , this error occurred : blockchain load error !!
newbie
Activity: 30
Merit: 0
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.0

After 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/releases

This would have saved a lot of time if the the github link on the Intense website was upto date.
member
Activity: 137
Merit: 10
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...
full member
Activity: 420
Merit: 184
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

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.

member
Activity: 181
Merit: 46
Lethean COO
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.
jr. member
Activity: 181
Merit: 2
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.
full member
Activity: 679
Merit: 103
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

?
jr. member
Activity: 181
Merit: 2
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:
Code:
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
Code:
{
  "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"
  }
}
jr. member
Activity: 181
Merit: 2
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!
newbie
Activity: 50
Merit: 0
How did INTENSE COIN develop this VPN? MYST is over a year ago, and the product hasn't come out yet. Do not the project team feel the intense competition?

We are in development stage, we should have our browser plug-in coming out until June and our main VPN client until August. We are not worried with competition, our focus is in developing the best product possible and we are very well in target Wink

And this is why I trust in intense devs, away try do the best Smiley
full member
Activity: 420
Merit: 184
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
full member
Activity: 219
Merit: 121
Lethean Developer
no pool is working properly ... i dont have even pending ballance on any pool ...

Pending balances will lag more right now because all pools are using the full 60 block maturity time since things are still a bit uncertain. That means your pending balance will always be 60 blocks behind (about 2 hours). At least that's how it worked with pre-Snipa22-based pool software, assuming the new pool software works the same.
full member
Activity: 219
Merit: 121
Lethean Developer
RE pools - Payments appear to be working as expected. Smiley

...
Release CLI binaries are available for Linux, Mac and Windows: https://github.com/valiant1x/intensecoin/releases/tag/v2.0.0
...

Two questions about migrating from 1.4.2 to 2.0.0:

1. Does the guide posted on Reddit still apply: https://www.reddit.com/r/IntenseCoin/comments/89gw15/guide_converting_your_141142_wallet_to_the_145/?st=JFSFQH68&sh=236d5812?

2. Usually one needs to nuke the existing blockchain in situations like this, but no mention was made of that in the above guide either for the 1.4.5 rebase or this one; an oversight or not?


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.
full member
Activity: 420
Merit: 184
...
Release CLI binaries are available for Linux, Mac and Windows: https://github.com/valiant1x/intensecoin/releases/tag/v2.0.0
...

Two questions about migrating from 1.4.2 to 2.0.0:

1. Does the guide posted on Reddit still apply: https://www.reddit.com/r/IntenseCoin/comments/89gw15/guide_converting_your_141142_wallet_to_the_145/?st=JFSFQH68&sh=236d5812?

2. Usually one needs to nuke the existing blockchain in situations like this, but no mention was made of that in the above guide either for the 1.4.5 rebase or this one; an oversight or not?

member
Activity: 144
Merit: 10
Pages:
Jump to: