Pages:
Author

Topic: [ANN][0.8.6.6] Hirocoin - X11 - Hardfork at Block 290,000 [Complete] - *New Dev* - page 5. (Read 36489 times)

full member
Activity: 338
Merit: 100
https://eloncity.io/
Is it a **New Dev** or a "New Dev"? Are there one or more? You're tagged as part of a team of Hirocoin "Dev"'s, so was someone added or replaced?

I'm taking over as lead developer. I am also waiting on hearing back from some people who may be joining the development team also.

I have dropped the fee from http://omargpools.ca/hiros to 0%. This is to encourage miners to switch to a pool that is running on the newest client.

really ?

quote from you to cryptoglance dev , if you cant do php how the hell is this one man shop gonna make this coin relive ?

its been 1 week now since last post , nothing fixed, no block explorer, and still those bad blocks.

Are you serious ?

"https://github.com/OmarxGx/cryptoGlance-web-app/compare/cryptoGlance:master...master"

Code:
 OmarxGx commented on cadfda2 on Jul 17
Sure, here's a screenshot. I also had some features I wanted to add to the
current app to support my pool, HiroPool.

I wanted to:
- include Hiropool.org/api as a supported pool option.
- Remove net hashrate and difficulty when HiroPool is selected to prevent
other from guessing which coin we're mining (protect profits)
- Call HiroPool's balance from Hiropool.org/hiro instead of HiroPool.org/api

If you could help me with those features it would be greatly appreciated.
I'm sure they would be quick edits but you'd know the code better than I do.
full member
Activity: 338
Merit: 100
https://eloncity.io/
well


getblockhash 353940
error: {"code":-2,"message":"Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."}

 gettransaction f2c849351ccd6cf8bf26ccddf04c8fa1099de92e9a196f90fd66a64af197701e error: {"code":-2,"message":"Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."}

something is really not working right....

 getinfo
{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 354050,
    "timeoffset" : 1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 1.41856790,
    "testnet" : false,
    "keypoololdest" : 1415235161,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
full member
Activity: 202
Merit: 100
Peers of other coins also not showing same blockheight with getpeerinfo. I think can just ignore the warning message (I am also still getting the "Displayed transactions many not be correct!.....") if you are using the correct wallet v0.8.6.6. I solo mined several hundred thousands of Hiro and sold in Poloniex without problem.
full member
Activity: 338
Merit: 100
https://eloncity.io/
also

getpeerinfo
[
    {
        "addr" : "182.92.0.128:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325666,
        "bytessent" : 49165,
        "bytesrecv" : 841656,
        "blocksrequested" : 2,
        "conntime" : 1415318171,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.5/",
        "inbound" : false,
        "startingheight" : 224000,
        "banscore" : 0
    },
    {
        "addr" : "110.143.228.78:9348",
        "services" : "00000003",
        "lastsend" : 1415325665,
        "lastrecv" : 1415325682,
        "bytessent" : 101961,
        "bytesrecv" : 405339,
        "blocksrequested" : 0,
        "conntime" : 1415318181,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351010,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "108.170.157.63:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325682,
        "bytessent" : 36939,
        "bytesrecv" : 108997,
        "blocksrequested" : 0,
        "conntime" : 1415318215,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351011,
        "banscore" : 0
    },
    {
        "addr" : "94.23.29.195:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325682,
        "bytessent" : 23146,
        "bytesrecv" : 78510,
        "blocksrequested" : 0,
        "conntime" : 1415319171,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351027,
        "banscore" : 0
    },
    {
        "addr" : "176.9.63.136:9348",
        "services" : "00000003",
        "lastsend" : 1415325665,
        "lastrecv" : 1415325682,
        "bytessent" : 69954,
        "bytesrecv" : 1086001,
        "blocksrequested" : 0,
        "conntime" : 1415319200,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351027,
        "banscore" : 0
    },
    {
        "addr" : "199.103.61.149:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325682,
        "bytessent" : 34470,
        "bytesrecv" : 117272,
        "blocksrequested" : 0,
        "conntime" : 1415319212,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351027,
        "banscore" : 0
    },
    {
        "addr" : "198.100.146.216:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325682,
        "bytessent" : 31351,
        "bytesrecv" : 88342,
        "blocksrequested" : 0,
        "conntime" : 1415319898,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351036,
        "banscore" : 0
    },
    {
        "addr" : "199.233.239.54:9348",
        "services" : "00000003",
        "lastsend" : 1415325682,
        "lastrecv" : 1415325683,
        "bytessent" : 16229,
        "bytesrecv" : 152810,
        "blocksrequested" : 0,
        "conntime" : 1415320375,
        "version" : 70013,
        "subver" : "/Satoshi:0.8.6.6/",
        "inbound" : false,
        "startingheight" : 351044,
        "banscore" : 0
    }
]



seems not on same height... im dropping this
full member
Activity: 338
Merit: 100
https://eloncity.io/
something is still wrong with this coin.


{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,
    "balance" : 341.00000000,
    "blocks" : 348377,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 2.00750786,
    "testnet" : false,
    "keypoololdest" : 1410164943,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

same here....
legendary
Activity: 1308
Merit: 1011
sr. member
Activity: 299
Merit: 250
What do I do? yesterday I sent poloniex 120000 HIRO, not reached. Today has updated wallet to version 0.8.6.6 and lost another 100000 HIRO tried to do-rescan-reindex , useless, in the transaction hangs on unconfirmed 120000 balance unconfirmed 0.024, where the rest of the coins I had on the balance in version 8.4.4/6 Huh The address remains the same, tried to delete the folder, all in addition to wallet - nothing helped
Detail transaction:
Статус/Status: 0/не подтверждено
Дата/Date: 05.11.2014 08:59
For: HTuAqXrW1sz4dygcdLZUtbRFyjHMX7xSFh
Дебет/debet: -120000.00 HIRO
Комиссия/fee: -0.035 HIRO
Чистая сумма/sum: -120000.035 HIRO
ID транзакции/id: 0a910d5f18652e7cfcb4900f2e1675e7f5615358383322a78d3a4c894549b60c
full member
Activity: 338
Merit: 100
https://eloncity.io/
newbie
Activity: 3
Merit: 0
something is still wrong with this coin.


{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,
    "balance" : 341.00000000,
    "blocks" : 348377,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 2.00750786,
    "testnet" : false,
    "keypoololdest" : 1410164943,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

newbie
Activity: 57
Merit: 0
Just letting everyone know that I'm still around. I've been extremely busy lately and apologize for not updating the community earlier.

Please could you explain :
-> witch protocol version is working,
-> witch wallet version is usable.

Because after having downgraded to 0.8.6.4 (protocol 70012) like asked in
https://bitcointalksearch.org/topic/ann086-hirocoin-x11-ngw-secured-blockchain-time-warp-limitation-516349
...it seems i loose all my sended coins !!!!

I'm not very happy......


Nobody is happy when you open one of those old wallets.

The current wallet is listed at the beginning of this thread.
"version" : 70013,
"subver" : "/Satoshi:0.8.6.6/",

Hiro stopped updating the old thread, so the information there is quite outdated.


newbie
Activity: 1
Merit: 0
Just letting everyone know that I'm still around. I've been extremely busy lately and apologize for not updating the community earlier.

Please could you explain :
-> witch protocol version is working,
-> witch wallet version is usable.

Because after having downgraded to 0.8.6.4 (protocol 70012) like asked in
https://bitcointalksearch.org/topic/ann086-hirocoin-x11-ngw-secured-blockchain-time-warp-limitation-516349
...it seems i loose all my sended coins !!!!

I'm not very happy......
hero member
Activity: 2170
Merit: 640
Undeads.com - P2E Runner Game
Just letting everyone know that I'm still around. I've been extremely busy lately and apologize for not updating the community earlier.

And now what?
legendary
Activity: 1148
Merit: 1000
Just letting everyone know that I'm still around. I've been extremely busy lately and apologize for not updating the community earlier.

Is there a working explorer for this coin?
sr. member
Activity: 392
Merit: 250
Just letting everyone know that I'm still around. I've been extremely busy lately and apologize for not updating the community earlier.
legendary
Activity: 1308
Merit: 1011
CoinKing is on the right fork and running the correct wallet version..

{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,


 getblockcount
326430


this matches what is on http://explorer.hiropool.org:3001/

coinking can't find a block for almost 3 hours now  Wink
i lost over150000 hirocoin from coinking because there are on old fork i think thery are now moving on to new fork now after 4 emails tell them this if you send your coins frome coinking now you will lose them and if they have changed you coins will now be unconfirmed and SORRY TO SAY THEY ARE DEAD COINS= STOP MINING AT HIROCOIN AT  COINKING UNTILL THIS IS FIXED I WILL POST HERE WHEN I HAVE  TRYED THERE FIX AND SENT COINS FROM THERE WALLET

dude, relax. We always go out of our way to make this stuff right. Give us a chance.....

*edit* we are still going through transactions manually. there were about ~6000 blocks found around the time of the fork. payout scripts are paused until then so we dont pay out blocks mined on the wrong fork. Everyone that is mining now is guaranteed to receive their coins once we turn the scripts back on.
WOW WHAT A LOAD OF BULL S H .. T I EMAILED YOU GUYS 4 TIMES TELLING YOU THAT YOU WERE ON WRONG FORK AND YOU TOOK 4DAY TO ANSER MY SUPPORT TICKET AND LOOK WHAT YOU SED QUOTE////
 Adam (COINKING)

Oct 19 08:05 PM          

please make sure that you are on the right fork. Our wallet has 65 connections and is at the correct block height. The developer abandoned this coin, i suggest you take a look at the OP which can be found here: https://bitcointalksearch.org/topic/ann086-hirocoin-x11-ngw-secured-blockchain-time-warp-limitation-516349

SO MY REPLY WAS/////
...
...
PS i can take pics of my email and post them to prove this

A wild goose chase. That's your coins down the drain.
Look for another pool or coin.
Try my p2pool: http://crypto.office-on-the.net:9408/
member
Activity: 61
Merit: 10
CoinKing is on the right fork and running the correct wallet version..

{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,


 getblockcount
326430


this matches what is on http://explorer.hiropool.org:3001/

coinking can't find a block for almost 3 hours now  Wink
i lost over150000 hirocoin from coinking because there are on old fork i think thery are now moving on to new fork now after 4 emails tell them this if you send your coins frome coinking now you will lose them and if they have changed you coins will now be unconfirmed and SORRY TO SAY THEY ARE DEAD COINS= STOP MINING AT HIROCOIN AT  COINKING UNTILL THIS IS FIXED I WILL POST HERE WHEN I HAVE  TRYED THERE FIX AND SENT COINS FROM THERE WALLET

dude, relax. We always go out of our way to make this stuff right. Give us a chance.....

*edit* we are still going through transactions manually. there were about ~6000 blocks found around the time of the fork. payout scripts are paused until then so we dont pay out blocks mined on the wrong fork. Everyone that is mining now is guaranteed to receive their coins once we turn the scripts back on.
WOW WHAT A LOAD OF BULL S H .. T I EMAILED YOU GUYS 4 TIMES TELLING YOU THAT YOU WERE ON WRONG FORK AND YOU TOOK 4DAY TO ANSER MY SUPPORT TICKET AND LOOK WHAT YOU SED QUOTE////
 Adam (COINKING)

Oct 19 08:05 PM           

please make sure that you are on the right fork. Our wallet has 65 connections and is at the correct block height. The developer abandoned this coin, i suggest you take a look at the OP which can be found here: https://bitcointalksearch.org/topic/ann086-hirocoin-x11-ngw-secured-blockchain-time-warp-limitation-516349

SO MY REPLY WAS/////
wow you looking on the old bitcointalk page here is the new one    https://bitcointalksearch.org/topic/ann0866-hirocoin-x11-hardfork-at-block-290000-complete-new-dev-787471 i suggest you do more home work and here are the new nodes as a puote I have submitted what I hope to be the final change to the github. I had some help from Raveneye to fix the bug causing the ConnectBlock error.

If you download the client you should be able to sync correctly to the current chain that I am on along with the clients who did not upgraded as it's the longest one. The client will disconnect at block 290,000 and MintPal will allow deposits and withdrawals on the new client as soon as the move to MintPalv2 is complete.

Please update to the new client and use this in your hirocoin.conf to sync to the correct chain with the new client.

UPDATED LIST OF NODES (v. 0.8.6)

addnode=93.178.105.197
addnode=176.28.13.164
addnode=67.215.11.195
addnode=188.226.194.191
addnode=110.143.228.78
addnode=54.193.113.180
addnode=192.99.32.187

Sorry for the inconvenience

The block explorer is now running correctly. It can be found here:

http://explorer.hiropool.org:3001/

There's an issue with the Insight Explorer and X11 hash function causing live block updates to cause a crash. Everything besides the latest blocks tab is functional. The correct block height is available at the top and syncs correctly.,,,
                                                                                YOU ARE ON THE WRONG WALLET HOW MANEY MORE TIMES I AM TRYING TO HELP YOU !!!WTF!! PLZ LOOK ON THE NEW THREAD ITS GOT 5 PAGES LOOK  MAY BE YOU WILL GET WHAT I AM SAYING,, THEN AND SEND SOME OF YOUR COINS AND YOU WILL SEE WHAT I MEAN I LOST OVER 150000 COINS BECAUSE YOU FORK IS DEAD?? DO I GET MY COINS BACKL FROM YOU I SENT THEM TO A EXCHANGES AND THEY WILL CONFIRM THEY DID NOT TURN UP?Huh PLZ LOOK IN TO THIS IM NOT FUCKING YOU ABOUT WHAT I SAY IS %100 TRUE EMAIL BACK WHEN YOU HAVE LOOKED IN TO THIS. THKS  ps the quote is from page 2 of the new thread you can find the link for the new thread on page 162 of the old thread. THKS
 AND A HOUR AFTER I SENT THIS FOR THE 2ND TIME THEY PUT A NOTE OUT ON THERE SITE AND THEN THEY CHANGED THE FORK AS YOU CAN SEE I HELPED THEM BY TELING THEM OVER AND OVER AGAIN, I DID NOT WANT ANYTHING FOR MY EMAILS JUST FOR THEM TO SAY THANK AND THEYS WERE SORRY I LOST OVER 150000 HIROCOINS AND 3DAYS MINING BUT NOT EVEN A THANKS NO REPLY EMAIL AT ALL,,,,    !!!THAT HOW COINKING SORT THINGS OUT!!!  PS i can take pics of my email and post them to prove this
newbie
Activity: 57
Merit: 0
with recommended nodes,

Where did you find them???

That should be listed on the OP

newbie
Activity: 57
Merit: 0
Coinwarz promptly to my request and are updating their client and will be relisting Hiro after re-sync... Hopefully they don't run into the problem Huh

On the other hand there is http://whatmine.com/. Although I have directed them to the new thread they running the wrong client and have not responded... Maybe some more complaints add to their incentive.
According to their listing somebody is still mining at 60+ MH on the old fork, that's probably causing some of our syncing problems.

Allcoin has updated the popup on their main page to point to the new thread by a simple request.
There are numerous links on various sites pointing in the wrong direction. You don't have to be on the dev team to request that pools or services update there links or clients, just a concerned Hirocoin supporter.
newbie
Activity: 57
Merit: 0
Sounds like you are connecting to old wallet that's corrupting your blockchain... luck of the draw maybe?
It's a little out of my ballpark but you could try this: Re-sync your wallet then turn it off. Delete your peers.dat file and then start it back up. It worked for me. I'm only getting connections to updated wallets now.
legendary
Activity: 1148
Merit: 1000
something is still wrong with this coin.


{
    "version" : 80606,
    "protocolversion" : 70013,
    "walletversion" : 60000,
    "balance" : REMOVED
    "blocks" : 328075,
    "timeoffset" : 0,
    "connections" : 18,
    "proxy" : "",
    "difficulty" : 1.90171498,
    "testnet" : false,
    "keypoololdest" : 1412827231,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}
root
Pages:
Jump to: