Pool down?
UP! But wallet.dat corrupted again, I already have skills repairing zcash wallets, it's ok. Up and running again. Nice! |
|
|
|
|
Turbostake is over 1 year old.
Looks like the domain is for sale.
"moneysupply" : 501766135.94717097
So at 0.00000001 a marketcap of 5 BTC.
|
|
|
|
No more shift mining  Will mining?
With the migration to Delegated POS mining has stopped. Would be good to know what the last official block number is. |
|
|
|
|
Node installation went fairly smooth. A bit of tweaking in config.json and my firewall and all good since I am not accessing it from localhost.
No doubt that it would be trivial for a person familiar with Lisk.
|
|
|
|
|
Black: Dark roast, Brewed, Nescafe or Nescafe espresso.
|
|
|
|
we went over 1100 masternodes at one point there  everything stable my end getting regular payouts from masternodes and staying in sync. a simple '=' messed up the chain last time. now we got a working test net no problems like that should happen again. I'm not sure the testnet would have found the last problem. More (friendly) eyes carefully looking at the code in github and the changes would help too. I think that that having possibilities for the p2p communication go through (or not go through) TOR, IPv4 and IPv6 can lead to groups of peers and masternodes to head off on their own chain when there are issues with connectivity. |
|
|
|
I would strongly suggest waiting for a statement from the Shift team about the use of web wallets.
I believe that the user has the best intentions on sharing this, and do not intend to affirm or discredit
the user's trustworthiness, IT practices or competence.Of course anything one does has risks and one would not accomplish anything if one tried to mitigate all risks. With a web wallet there is a longer chain of trust, involving much more than the person who sets up the server. If you have more SHIFT or other crypton than you would want to loose, consider carefully who you would like to trust. Keeping the chain short reduces the risks. In addition to a person who sets up a web wallet server, the following and more need to be trusted to have impeccable security practices. - Hosting provider servers, storage, network, DNS - Virtualization Platform (which may have a malicious VM, may be same ) - Certificate Authority - OS and Utilities( Host and VM) - All other software the - Network - ... Then there is your end - Your Computer's / Tablet's / Phones manufacturer, importer, retailer - OS - Web Browser - Antivirus and all other software / apps running on it. - ...
|
|
|
|
Do you mean http://shf.mskpool.ru ? It's been more than eight hours since last block was found not sure what's wrong with there pool I hope many people are not mining, so only it is talking lot of time for blocks. About 62 minutes between block 792500 and 792600. So about 37 seconds per block. So normal. Difficulty is guite high, 94115918415. Note sure what the highest was, but at block 790600 (Wed Oct 5 08:56:05 UTC 2016) it was up to 106081102438. |
|
|
|
i also have a backup from a node in sync with info page from about a hour ago
just send me a pm if you need the link for download, maybe this will help
I've just restarted my other 10 masternodes which I've left untouched since it got stuck today. 5 out of 10 came match the MN info page. The other 5 do not. So I got a good copy now.  But yeah, this is with assumption that MN info page is indeed the correct chain. (I hope it is!) lol we all hope so *fingers crossed* A problem with peer connectivity I suppose. I am not up to the same height as the hash Jakiman posted but I suppose we are forked again. |
|
|
|
Hi,
controller wallet and 3 Masternodes all stuck at 324999
regards
Same here... For me, stopping and restarting the masternode was enough. ( darknet-cli stop ;darknetd ) Stuck and up to date nodes had the same hash: darknet-cli getblockhash 324999 fa60845e7d34eb5cfa530e48633c6e2d75a65828b733f98092f0e2bc929e86ce Up to date nodes are the same as the masternode info page: darknet-cli getblockhash 325563 c9a79ea752d8d73748d247c7ca4a3537ffc1cccd0337c5e11e63bd8521cdacaf |
|
|
|
Whatever I do I cannot get Shifthub to sync I get the ''Your connection is restricted. Please, open 15441 port on your router
or configure Tor to become full member of Phantom network.'' message
I have allowed this port in router, I've also tried in tor to no success, Any ideas?
This has nothing to do with ShiftHub nor your router, nor phantom. Start gshift.exe with the console command, (like this... >gshift.exe console) and paste the following commands.. admin.addPeer("enode://3863f4c5df46088ccb1dff3a3256dfc61faf6d721b2e6db06f3d4e43461d824c423b5dc87aab17c6f173884f8010eafdb6f62bbc5747311577d29aa4457d2546@178.33.228.14:13900") admin.addPeer("enode://cef471e6f0e21022c6466f7a12c4c6b76810ec560f041c419f26cf6a995e07da3dcde4679d476461115cbebfb4161175e9091e7585753af41a2f79ebe32a9d9f@83.220.169.87:53900") admin.addPeer("enode://d7b2a4a966de561232a0e8945a2accd3fcbf4c580f2a5a15697da6792d2c2c502847b93a75a4476f32a08ddd1cb87f52e4037f2e6f9b33ed1fbee8ee6ed859a7@109.185.141.150:53900") How do I get this to stick after a reboot? Can add the list to .gshift/static-nodes.json See here for the format: https://github.com/ethereum/go-ethereum/wiki/Connecting-to-the-network#static-nodesHere's how to get the data: http://ethereum.stackexchange.com/questions/8828/how-can-i-extract-create-a-list-of-peers-from-my-syncing-geth-node-to-manually-pIf you think gshift is trying too hard to connect to other peers, once you have a good list of static nodes and good connectivity, you could look into trying the "--nodiscover" option when running gshift. Also, make sure your clock is correct (within 15 seconds). You will have trouble connecting to other nodes if your clock is off. If you are running Linux, look into "ntp". Now idea about windows. |
|
|
|
for windows is sttill using old wallet for staking?? im still holding my kr
Send your old coins to Bittrex for the swap You cannot send coins to Bittrex. The old KR chain is not running. I will be doing a manual swap of KR coins held off-exchange. Swap instructions will be posted soon. Hi, It looks like the chain IS running still... it appears that two of the seednodes are still up (178.33.51.154:...) gkr --exec "admin.peers" attach |grep remote remoteAddress: "109.70.186.58:17171" remoteAddress: "178.33.51.154:17171" remoteAddress: "178.33.51.154:17172" Have you decided at which point in time the ethereum based chain is no longer official. That chain was abandoned weeks ago.... at the time of the second big attack/extortion/blackmail. A scrypt pos chain has been running since then. That didn't really answer the question. A little digging... and I found this message from Sept 4th. Only KR mined prior to the Bittrex shutdown (5:04PM EDT 2-Sept-2016) https://bitcointalk.org/index.php?topic=1368118.msg16146806#msg16146806The chain does contain valid data, up to a certain block number. So it has some value and should be maintained / archived instead of abandoned. It would be really cool if the scrypt PoS daemon could support the old ethereum based keystore and addresses. Then the balances could be migrated, the to the PoS chain and all that would be needed would be to copy over the keystore and enter a passphrase and have coins already there. I guess we wait for more information about the swap. What happens to unclaimed coins or extra coins made for PoS? Will there be a way to map old addresses / final balances to the PoS chain? |
|
|
|
Ok testnet wallet running here. Can I please have some tdnet love here? yBh7yX6ifGWLiobLiug7J9HiJXXpMgHsTH
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
I'll send a bit. Don't spend it all in one place. |
|
|
|
for windows is sttill using old wallet for staking?? im still holding my kr
Send your old coins to Bittrex for the swap You cannot send coins to Bittrex. The old KR chain is not running. I will be doing a manual swap of KR coins held off-exchange. Swap instructions will be posted soon. Hi, It looks like the chain IS running still... it appears that two of the seednodes are still up (178.33.51.154:...) gkr --exec "admin.peers" attach |grep remote remoteAddress: "109.70.186.58:17171" remoteAddress: "178.33.51.154:17171" remoteAddress: "178.33.51.154:17172" Have you decided at which point in time the ethereum based chain is no longer official. |
|
|
|
For those who are having trouble... did you try this? My masternodes and wallet have been fine since doing this. Dev Update SnippetNew wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday. Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs. In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches. If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes) addnode=173.245.158.8
addnode=68.108.10.35
bantime=50 MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html |
|
|
|
Does this mean Shift will be a Lisk fork rather than an Etherium fork?
Moving to the Lisk codebase could be a better description than fork as the genesis blocks used are different than Ethereum's or Lisk. Shift is still Shift, the additional functionality is to be ported to use Lisk's software instead of Ethereum's as a basis. |
|
|
|
|
Wallet forked, all my mastrnodes ok I think..
Staking on.
Wallet:
$ darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
Masternodes:
darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
darknet-cli getblockhash 311244
15e3842967038da2336fa829bafe19e8dbece41d3f4b298b30469d4ca13eeed6
|
|
|
|
|
Ok... wasn't sure at first the blocknumber is going up and down on my wallet.
|
|
|
|
|
Good:
darknet-cli getblockhash 309193
04389d2830e45c2abe98a0747c08914b097ac96f6696963eb6dced1c56824201
darknet-cli getblockhash 309108
82780640ccdb595cbf08e708dd9410ef8e1f936bdb26fe5b07fc0741c845e955
darknet-cli getblockhash 309061
657535f618bf360470653bb38bebf8b734606a4e25bfb49684a98fc9cfaa7c3c
Stuck:
darknet-cli getblockhash 309193
941b5044c32417a863e7eede463af51adb4bbbd4b6eac113269f3ec38a680d86
darknet-cli getblockhash 309108
cab4f64d67b75ac1053b37e72dd40a625b0baf27db77403e38e45228510ae238
darknet-cli getblockhash 309108
22b87da59f7534549384a7cae49e79a93413a0dab97e93508eaf3c2a632fa7a5
darknet-cli getblockhash 309108
3813cf7b05fd63e91970acd041d38bc8524f6b139cca226ea6f38109e773221c
darknet-cli getblockhash 309061
758e17712ddaabf0542eaf54467f399025feb5ed381d4449762a5e5d24933a3d
darknet-cli getblockhash 309061
38ce11cbdf1c2cc5efa73ea6cc1a41ce33daaeef6b47b9fbab625a88a0d3edd2
darknet-cli getblockhash 309061
af6df5769d2df16f68afc40da8d034b5e13471a3782d41ab523e9c4e70cd7e57
|
|
|
|
|
My masternodes all agree here...
darknet-cli getblockhash 309010
5b385bdbe977508f3838d7e6af28ac5c70c49c52d64fdf7b034733837195e701
Over half are stuck.
Others agree on this...
darknet-cli getblockhash 309188
9d2fbd097070c7d2ea0f80faf300c860efaf843419d46acb48cbb03bca5a50e7
Will try adding some good peer connections.
|
|
|
|
|
Show Posts
