23 Skidoo CHAO Information

[infernoman]

0.11.1 is me, working on testing changes to fix some issues i found. it wont be released officially until AUXPOW starts at block 825000

I can not import privkey from CROC coin

error: {"code":-5,"message":"Invalid private key encoding"}

any idea?  to configure merged mining I should make priv key shared between 2 coins

There is no need to import a key from another wallet when merged mining. but you do need the proper software to do it.

[startsts]

0.11.1 is me, working on testing changes to fix some issues i found. it wont be released officially until AUXPOW starts at block 825000

I can not import privkey from CROC coin

error: {"code":-5,"message":"Invalid private key encoding"}

any idea?  to configure merged mining I should make priv key shared between 2 coins

There is no need to import a key from another wallet when merged mining. but you do need the proper software to do it.

My software ( https://github.com/KillerByte/node-merged-pool )  needs one shared key.
I'm not expert of JS to change the code.   So could you explain why I can not import private key from CROC coin?

[infernoman]

UPDATE FROM CRYPTOPIA:

The only way we will keep a 51%'ed coin listed is if the developer or community etc is able to remunerate our user balances.

We are down about 0.03 CHAO so if think that this is possible to send us we can keep it listed (of course we would also be able to provide you exact amount, our user balances and wallet balances etc.)

[startsts]

UPDATE FROM CRYPTOPIA:

The only way we will keep a 51%'ed coin listed is if the developer or community etc is able to remunerate our user balances.

We are down about 0.03 CHAO so if think that this is possible to send us we can keep it listed (of course we would also be able to provide you exact amount, our user balances and wallet balances etc.)

too much   
it's about 5000$ 

[startsts]

WTF,  I sent small amount for test and see that fee is there:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00001066,
        "vout" : 0,
        "fee" : -0.00013910,
        "confirmations" : 0,
        "txid" : "b11b71d4f77cb2d532149a210f1b82fb4410831048476cfc8cff7be637542d23",
        "walletconflicts" : [
        ],
        "time" : 1504885836,
        "timereceived" : 1504885836
    }

it is after that I set paytxfee 0.00000001


{
    "version" : 110000,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00287400,
    "blocks" : 771598,
    "timeoffset" : -3,
    "connections" : 15,
    "proxy" : "",
    "difficulty" : 1757108.53301925,
    "testnet" : false,
    "keypoololdest" : 1504688441,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000001,
    "relayfee" : 0.00001000,
    "errors" : ""
}


You should explain this behavior! I stop skidoo daemon on Cryptohub until you resolve the problem

[heratys111]

WTF,  I sent small amount for test and see that fee is there:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00001066,
        "vout" : 0,
        "fee" : -0.00013910,
        "confirmations" : 0,
        "txid" : "b11b71d4f77cb2d532149a210f1b82fb4410831048476cfc8cff7be637542d23",
        "walletconflicts" : [
        ],
        "time" : 1504885836,
        "timereceived" : 1504885836
    }

it is after that I set paytxfee 0.00000001


{
    "version" : 110000,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00287400,
    "blocks" : 771598,
    "timeoffset" : -3,
    "connections" : 15,
    "proxy" : "",
    "difficulty" : 1757108.53301925,
    "testnet" : false,
    "keypoololdest" : 1504688441,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000001,
    "relayfee" : 0.00001000,
    "errors" : ""
}


You should explain this behavior! I stop skidoo daemon on Cryptohub until you resolve the problem

Hey,

I think what occurred is explained here and would be consistent with the mythos/head-space of this coin: https://cryptocurrencytalk.com/topic/8154-23-skidoo-chao-information/ ; specifically, on the ninth line of this announcement (I'm quoting both lines 8 and 9 to provide full context):

     "1/1000th of a Skidoo is a Chao, and this is the default method of divding Skidoo. Default RPC Port is 10023. The Discordian Gravity Well was directly ripped off from Kimoto and as such, the difficulty is self-regulating. Blocks take 23 confirmations to be valid and to be           infuriating, there is a 5000 milliChao limit to how much you can send at once. Oh and plus a silly fee structure that could cost you as much as you'd like to send in fees payable to the Discordian network of Skidoo pushers."

Every time I've sent Chao to my wallet from Cryptopia I've lived in dread of this threat (it's a little malicious, somewhat-nudgingly-spiteful, and absurd at the same time).  My "listtransactions" within the daemon records seven receives from the exchange to one of of my wallet addresses (I've used/generated a different receive address each time to circumvent rich-list and taint-analyses).  Within my limited experience, I haven't yet had the transaction fees eat my transaction alive; but I'm asserting or hypothesizing that this might have occurred in this particular instance... alas.

I'm offering to make you whole/sound again.  Judging by your balance in the second block of code, my current Chao-horde is somewhat larger than yours.  Did you lose 0.00001066 CHAO or 0.00013910 CHAO in your test-send???  Please PM me a skidoo address of yours and I'll reimburse you for your loss (as I don't want this somewhat maledictive circumstance to unduly color your experience with this coin -- insofar as you are hosting the only exchange market for CHAO as Cryptopia seem to have decided to be a vigorous/flagrant collective of assholes).

Also, after I've reimbursed you for your loss, please try your test-send/experiment again.  My expectation is that transactions of CHAO should typically send like any normal coin but there are a certain percentage of transactions that fall outside a normal curve, or have "tail-risk" -- I don't know if it's a helpful metaphor but look at https://en.wikipedia.org/wiki/Black_swan_theory .

[startsts]

Did you lose 0.00001066 CHAO or 0.00013910 CHAO in your test-send???  

Since I set fee 0.00000001  (its per kilobyte)   in case of make transaction  0.00001066 in worst case will be used 1066 unspent inputs of minimum reward and the fee should be aprox 0.00000320.  Actually it will use lower count of inputs since I have a lot of bigger unspent.

Anyway I don't understand how it could calculate that fee.

The problem is How can I pay to my miners?  If to sent 2$ i should pay 20$ fee

My address is zXuP1xCL4ZXXyPbhmd4iduTAryzCWyRifu   that transaction still having 1 confirmations, no new blocks for 23 hours,  so I don't why we are talking about,  skiddoo seems dead


Tried once more,  even with 0 fee set,  the problem persists

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00001011,
        "vout" : 1,
        "fee" : -0.00015085,
        "confirmations" : 1,
        "blockhash" : "00000000000000744c273970c17ad41b6d66f507c444a1623cef19d3b0651426",
        "blockindex" : 1,
        "blocktime" : 1504973414,
        "txid" : "fc4b9343a7e9afbbca121af69815fb6738fdfeb1f8bbb09a8e2b0c262c0d3c60",
        "walletconflicts" : [
        ],
        "time" : 1504973407,
        "timereceived" : 1504973407
    }

[startsts]

Raw transaction situation:

I try to send 0.00001000  with fee 0.00000011   (I use one input of 0.00001011)

error: {"code":-26,"message":"66: insufficient priority"}


Finally seems that minimum allowed fee is 0.00001000 for kb

I could send this way:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00000700,
        "vout" : 0,
        "fee" : -0.00000311,
        "confirmations" : 0,
        "txid" : "7677ff656c5b772c99df4b0cf56bdf67db6f246f71ef82f7e8da749acc79e4d9",
        "walletconflicts" : [
        ],
        "time" : 1504997860,
        "timereceived" : 1504997860
    }



But how a POOL  can exist if to use one unspent  0.00000001 or 0.00000010  I should pay 0.00000200 of fee?
(One unspent is about 200 bytes.  )
Now I understand -  there are no new blocks since pool (I think zpool) mines it only when there are unconfrmed transtacion in memory.

It was the main idea of coin?  To generate only blocks with transactions in it?

[don2018]

Here another airdrop you guys might be interested in, closes on September 14th so hurry, no much time left

Just sign up for newsletter and get 10 dollars free

Follow the link TO JOIN

http://bounty.authorship.com/ref/N8951700

[heratys111]

Raw transaction situation:

I try to send 0.00001000  with fee 0.00000011   (I use one input of 0.00001011)

error: {"code":-26,"message":"66: insufficient priority"}


Finally seems that minimum allowed fee is 0.00001000 for kb

I could send this way:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00000700,
        "vout" : 0,
        "fee" : -0.00000311,
        "confirmations" : 0,
        "txid" : "7677ff656c5b772c99df4b0cf56bdf67db6f246f71ef82f7e8da749acc79e4d9",
        "walletconflicts" : [
        ],
        "time" : 1504997860,
        "timereceived" : 1504997860
    }



But how a POOL  can exist if to use one unspent  0.00000001 or 0.00000010  I should pay 0.00000200 of fee?
(One unspent is about 200 bytes.  )
Now I understand -  there are no new blocks since pool (I think zpool) mines it only when there are unconfrmed transtacion in memory.

It was the main idea of coin?  To generate only blocks with transactions in it?

Yeah, I may have leapt to the wrong conclusion above... the relay fee is 0.0000100 CHAO (so the sent amount has to be larger than that to have any rationale to send it).

Zpool seems to have mined the last five blocks.  I think Wmikrut was mining its own private orphaned chain for a bit in the last 24 hrs too.

[startsts]

Raw transaction situation:

I try to send 0.00001000  with fee 0.00000011   (I use one input of 0.00001011)

error: {"code":-26,"message":"66: insufficient priority"}


Finally seems that minimum allowed fee is 0.00001000 for kb

I could send this way:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00000700,
        "vout" : 0,
        "fee" : -0.00000311,
        "confirmations" : 0,
        "txid" : "7677ff656c5b772c99df4b0cf56bdf67db6f246f71ef82f7e8da749acc79e4d9",
        "walletconflicts" : [
        ],
        "time" : 1504997860,
        "timereceived" : 1504997860
    }



But how a POOL  can exist if to use one unspent  0.00000001 or 0.00000010  I should pay 0.00000200 of fee?
(One unspent is about 200 bytes.  )
Now I understand -  there are no new blocks since pool (I think zpool) mines it only when there are unconfrmed transtacion in memory.

It was the main idea of coin?  To generate only blocks with transactions in it?

Yeah, I may have leapt to the wrong conclusion above... the relay fee is 0.0000100 CHAO (so the sent amount has to be larger than that to have any rationale to send it).

Zpool seems to have mined the last five blocks.  I think Wmikrut was mining its own private orphaned chain for a bit in the last 24 hrs too.

so it means block rewards lower than 0.00001000  are dust,  why those few rewards exist?

[PeterTheGrape]

UPDATE FROM CRYPTOPIA:

The only way we will keep a 51%'ed coin listed is if the developer or community etc is able to remunerate our user balances.

We are down about 0.03 CHAO so if think that this is possible to send us we can keep it listed (of course we would also be able to provide you exact amount, our user balances and wallet balances etc.)

There are a few issues.

1) Is the issue fixable or is it going to keep happening? If it has been fixed then I'll contribute a fair amount. If it hasn't been fixed and is going to keep on happening then better to let the coin drop and wait til the problem is clear.

2) What exactly happened? Does 51% mean a 51% attack and somebody changed the blockchain or made extra coins? Why would they relist it if it were an attack likely to happen again and again? Then every time it happens people will need to pay the exchange however much is lost?

A cool coin and potentially very useful but if an attacker can take coins at will then no sense having it on an exchange.

[PeterTheGrape]

...


Also, and importantly, for anyone else with a stake, this beloved CHAO-coin is being dropped from Cryptopia -- so anyone affected really ought to get their coins off that exchange.  Hopefully there'll be news about other exchanges soon (so that there is an open market for 23-Skidoo in the long term).

Why is Cryptopia dropping Chao?

As long as the coin is not hacked or hijacked exchanges should not be a problem soon.

 

Because for some reason they seem to think im a bad actor on the network. http://prntscr.com/ghwm8x

Sorry, just reading back in the thread and got to this.

So the coin has not been hijacked, but somehow they lost 0.03 chao?

How did they lose that?

[raoufgx07]

You have to work on it because it is rare And famous
it's not
dogecoin hhhhh,Make it work

 

[startsts]

Well I close pool at cryptohub since its mining is impossible due to this high tx fee.
But market is working:  https://cryptohub.online/market/CHAO/

I set withdrawal fee 0.00001000,  I don't know if it will be enough.

[4oshio]

skidoo CHAO,no list on cryptopia now...

[wmikrut]

Raw transaction situation:

I try to send 0.00001000  with fee 0.00000011   (I use one input of 0.00001011)

error: {"code":-26,"message":"66: insufficient priority"}


Finally seems that minimum allowed fee is 0.00001000 for kb

I could send this way:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00000700,
        "vout" : 0,
        "fee" : -0.00000311,
        "confirmations" : 0,
        "txid" : "7677ff656c5b772c99df4b0cf56bdf67db6f246f71ef82f7e8da749acc79e4d9",
        "walletconflicts" : [
        ],
        "time" : 1504997860,
        "timereceived" : 1504997860
    }



But how a POOL  can exist if to use one unspent  0.00000001 or 0.00000010  I should pay 0.00000200 of fee?
(One unspent is about 200 bytes.  )
Now I understand -  there are no new blocks since pool (I think zpool) mines it only when there are unconfrmed transtacion in memory.

It was the main idea of coin?  To generate only blocks with transactions in it?

Yeah, I may have leapt to the wrong conclusion above... the relay fee is 0.0000100 CHAO (so the sent amount has to be larger than that to have any rationale to send it).

Zpool seems to have mined the last five blocks.  I think Wmikrut was mining its own private orphaned chain for a bit in the last 24 hrs too.

Am I orphaned?

I see my wallet height matches https://chainz.cryptoid.info/chao/ within a block or two.
If I was orphaned I would think it would be way off.

[infernoman]

skidoo CHAO,no list on cryptopia now...

Once i get enough funds together from mining. I will get cryptopia back online.

Also wmikrut, you may be. Just found some information relating to the fork and syncing on the windows client that most likely affected mining as well. Pushed my changes to Unobtanium and PR already. just about to push the changes for skidoo

[infernoman]

Raw transaction situation:

I try to send 0.00001000  with fee 0.00000011   (I use one input of 0.00001011)

error: {"code":-26,"message":"66: insufficient priority"}


Finally seems that minimum allowed fee is 0.00001000 for kb

I could send this way:

{
        "account" : "",
        "address" : "zAqG9VXQuAZhmAooSehTo6rkWJF6CSb9w4",
        "category" : "send",
        "amount" : -0.00000700,
        "vout" : 0,
        "fee" : -0.00000311,
        "confirmations" : 0,
        "txid" : "7677ff656c5b772c99df4b0cf56bdf67db6f246f71ef82f7e8da749acc79e4d9",
        "walletconflicts" : [
        ],
        "time" : 1504997860,
        "timereceived" : 1504997860
    }



But how a POOL  can exist if to use one unspent  0.00000001 or 0.00000010  I should pay 0.00000200 of fee?
(One unspent is about 200 bytes.  )
Now I understand -  there are no new blocks since pool (I think zpool) mines it only when there are unconfrmed transtacion in memory.

It was the main idea of coin?  To generate only blocks with transactions in it?

Yeah, I may have leapt to the wrong conclusion above... the relay fee is 0.0000100 CHAO (so the sent amount has to be larger than that to have any rationale to send it).

Zpool seems to have mined the last five blocks.  I think Wmikrut was mining its own private orphaned chain for a bit in the last 24 hrs too.

Am I orphaned?

I see my wallet height matches https://chainz.cryptoid.info/chao/ within a block or two.
If I was orphaned I would think it would be way off.

You can pull and rebuild now. I've got my miners pointed your way. should be no need to reindex.
Do a "git checkout chainID" just incase. I've switched that to the default branch though.

Once im sure we're all on the right fork and working together then ill get a windows client released.

[wmikrut]

Cloning chainID and compiling now.
I have stopped the pool while I work on this.