Topic: 23 Skidoo CHAO Information - page 6. (Read 39881 times)

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?

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
    }

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 .

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

too much   
it's about 5000$ 

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.)

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?

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

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

oh..ok...
i hope is solo works too..thanks

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

/Skidoo:0.11.0/           node list   70003   5   41.7 %   41.7 %
/Skidoo:0.10.1.1/   node list   70002   3   25.0 %   66.7 %
/Skidoo:0.10.1.1/   node list   70003   1   8.3 %   75.0 %
/Skidoo:0.11.1/           node list   70004   1   8.3 %   83.3 % ==>>NEW
/Skidoo:0.9.0.1/   node list   70001   1   8.3 %   91.7 %
/Skidoo:0.9.2/           node list   70002   1   8.3 %   100.0 %

new ver? Skidoo:0.11.1..oh god...

Hmm... I opened up the glorious skidood terminal today and "getinfo" output:

"
{
    "version" : 100101,
    "protocolversion" : ...
...
...
unlocked_until" : 0,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000
"errors" : "Warning: This version is obsolete, upgrade required!"
}"

Also, https://chainz.cryptoid.info/chao/#!network lists the network clients in the past 24 hours as follows:

Sub-version              Protocol        Count            Network Share

Skidoo:0.11.0/           70003          5                41.7 %   41.7 %
/Skidoo:0.10.1.1/      70002           3                25.0 %   66.7 %
/Skidoo:0.10.1.1/       70003          1                8.3 %   75.0 %
/Skidoo:0.11.1/          70004          1                 8.3 %   83.3 %
/Skidoo:0.9.0.1/         70001          1                 8.3 %   91.7 %
/Skidoo:0.9.2/           70002           1                 8.3 %   100.0 %

If I understand, Infernoman's build is 0.11 ??   Does that version also take into account Vlad9Vlad's work to ensure it's not corrupt and rife with trojans or other malware?
For a superficial, aesthetic question: if I someday get the gui compiled in my Linux distro will it not look like that of Hagbard Celine's post #9 on this thread? If not ***that's too bad    as that wallet is phenomenal-looking IMO **.

I'd conjecturing that the merge-mining capability should help make this coin more robust by drawing more entrants into mining this -- which should also justify (in a recursive/feedback-loop sorta way) the high prices as it is far rarer than other coins from circa 2014 e.v.  Regarding the robustness, I stumbled across something a few days back about the futurist/Extropian/Satoshi-Nakamoto-correspondent (or an alias of SN?) Hal Finney opining:

>In late 2010, he discussed the relationship between the profitability of the process and the overall health of the network. He argued for a healthy balance to
> ensure that network participants remain as concerned about security as they are about making money
> ...
> In January 2011, he offered additional thoughts on the topic, suggesting that the cost of bitcoin mining should be somewhat prohibitive.
> He voiced concern that a wealthy mining operation could theoretically take over the network, and pointed to the expenses associated with
> mining as a positive element of the process.   Finney noted:
> “Ultimately it's good for the network for mining to be expensive. It makes it that much harder for a well financed attacker to dominate the network.”
 (source: https://www.coindesk.com/hal-finney-bitcoin-words/ ).
 
So, to save the CHAO I've socked away (bought off Cryptopia the last few months) as I expect I will move away from vrsn 0.10.1.1: would the following link be roughly the process I'd want to do (hopefully it's fool-proof because I don't want to goof it up):
        https://cryptocurrencytalk.com/topic/2023-quick-guide-how-to-rebuild-a-qt-wallet-if-you-lost-your-coins/ ??
 (i.e. backup wallet.dat [unencrypt it first I guess?? as I use the passphrase feature on all coins] do the dumpprivkey stuff that link describes, and then go ahead and git clone infernoman's source, check the hash and try to compile it (hopefully with a GUI/QT , crossing my fingers that it looks as slick and distinctive as Hagbard Celine's post showed) and hope I still have access to my Chao-horde.   I'm probably going to park some coins at Cryptohub (but perhaps not the full chunk).

Also, as my client is running off the terminal only, would there be any other changes I would want to make in the directory that contains:
blocks      database  debug.log          peers.dat    skidoo.pid
chainstate  db.log    fee_estimates.dat  skidoo.conf  wallet.dat ?

Aside from saving a backup copy of the files in that directory -- except maybe "blocks" as I think that's the unpruned-blockchain.  I'd allow the new installation to rebuild it's own version of it (the .skidoo directory in Unix's nomenclature)  and then somehow get it aligned with my backup wallet (I think this is possibly the reindexing that people were referring to? More likely it's the dumpprivkey from the walkthrough site that I just mentioned)

Any constructive suggestions or insight by someone more adept at this would be appreciated.    Much of the discussion earlier in this thread regarding the reindexing and AUXPOW  is beyond my knowledge or experience at this time (I need kind of a dumbed-down walkthrough at this point).

@mathi usted problamente necesita mover los coins a otro wallet o es possible que estaran en limbo/hostage en el intercambio.   

Hey startsts.
If you check out the earlier pages of this thread, you'll see the really strange payout. It follows the law of fives which is based off some mythology Blazr2 apparently had an interest in.
The smallest payout is .00000001.
Not every block has a reward either.

Here is the original thread from the now defunct 23skidoo.info website the original dev put together:

------begin snippet--------

A very odd SHA256-token indeed, if even to be called that. This is the only listing of its specifications, as provided by Malaclypse the Third only to be released upon you in this time:
 
23 total skidoo, ever. No 'pre' mine/special blocks, however the chain has already undergone its first offerings to Eris. The reward structure confirms to the Law of Fives and the 17 and 23 Enigmata and is as so:
 
If the block height is divisible by 2, the offering is rewarded with .00000001 Skidoo
If its not divisible by 2, but it is by 3, the offering is rewarded with .0000001 Skidoo
If its not divisible by 2 or 3 but ends in a 5, the offering is rewarded with .000001 Skidoo
If it doesn't conform to the Law of Fives, but is divisible by 17 or 23, the offering is .00001 Skidoo
All other blocks don't pay, yea that's right, 0. It will take nearly 400K of blocks to have 1 whole Skidoo - A LIE! - See davethehat's spreadsheet in thread.
 
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.


-------end snippett---------

If you go to the wayback machine and search for 23skidoo.info, you can find a little more information. I can't remember if it had Dave's spreadsheet or not. Here is the link with web snippets of the website's history. DO NOT GET THE CLIENT AT THE WAYBACK MACHINE LINK. IT"S VIRUS RIDDEN. (Sorry about the caps, not trying to scream, just want to make sure anyone reading this thread understands the importance of not using the old client from the wayback machine download link.)

wayback machine link for old 23skidoo.info:  https://web.archive.org/web/*/23skidoo.info

Infernoman has posted some links for getting the newer client on his github site.
As far as setting the tx to .00000001, I don't see why not based on the lowest payout of the law of fives being .00000001, but I'd rather have Infernoman confirm this as you have seen in my previous posts, I'm not a code wizard, but can handle some simple debugging and minor corrections to code compiling issues.

Since CHAO is SHA256 and based off of bitcoin code, the tx fee you mention should be fine. See this site regarding fees. It might offer a little insight.

https://bitcoinfees.21.co/

Hope this helps, but the minimum transaction is .00000001 as that is part of the law of fives least possible payout, if the block pays out at all.
Maybe infernoman can confirm the .00000001 tx fee.

Please respond to me

-What is minimum allowed transaction amount?
-What is minimum tx fee? If I set "settxfee 0.00000001" is ok?

The whole reason chao needs this is because it was 51% attacked, and that is why its being removed from cryptopia. Nothing to do with the update.

i try to solo direct on gui wallet qt or src (skidood),not working on ver .11
but i try to unomp and nomp is connected on daemon...
need help please.... to solo direct to wallet.
thank you

is solo still ok on ver .11?why i'm not connect on daemon?in ver.11?

I almost added skidoo to cryptohub.
But I have questions:

-What is minimum allowed transaction amount?
-What is minimum tx fee? If I set "settxfee 0.00000001" is ok?
-What is average block reward to set at calculator

You can be trading skidoo at CryptoHub soon.