Can the most recent TRK and HYP releases for the public stake with both open? If not, what fix is required?

rpcport=18875
port=18876

192 blocks..now,i can find 8-10blocks a day,so,the difficulty will chang after 24 days?

the expected time to block  is too long(3.15h per block),this may cause some questions.we send coin from wallet to poloniex needs 6 confirm(at least 18.9 hours ).So,I think we can chang the reward of a block(eg. 0.48 to 0.048)and chang the expected time of a block(eg.3.15h to 0.315h)

Guys I need help. My old wolf wallet stops syncing on August 2nd block 52836. Ive downloaded the latest version dated May 15th 2014, Deleted ALL but wallet.dat in roaming, downloaded latest .conf. Just wont go any further. Now I know that wolf 2.0 is coming out (Adrenaline), and Ive read the OP and gone to the site, does NOT say anything about exchanging old coins for new ones. What am I missing?

Thanks. Some much needed improvements, if possible:
- align the amounts on the decimal point so that 80000 doesn't look bigger than 400000. Easy way to do it: devote 7 characters for the integers, so 16 characters for the amount (seven, dot, eight)
- add a thousands separator (comma)

The current richlist is not sorted and has a lot of duplicated addresses (usually with different amounts). For a not-so-faithful snasphot richlist that actually makes sense, check my manual richlist, extracted from uni.me. I won't update it.

HYP Richlist (manual, unmaintained)

I am sorry i didn't know that we have one so scratch that and just rich list hahah

Does anyone know whats happening with cryptsy and if coins can be deposited or withdrawn from there?

Anyone aware of a working block explorer for this coin.

Could some people give me their latest block along with the blockhash?

Thank you,

Ryan @ Bittrex

myserver$ ./OpecCoind getpeerinfo | grep height
        "startingheight" : 98687,
        "startingheight" : 98688,
        "startingheight" : 98688,
        "startingheight" : 98688,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98689,
        "startingheight" : 98692,
        "startingheight" : 98692,
        "startingheight" : 98693,
        "startingheight" : 98693,
        "startingheight" : 98693,
        "startingheight" : 98694,
myserver$ ./OpecCoind getblockhash 98693
475069fdaf8fb7110960bfc3ee4d93d1f88bbfd941413adf9a70158f6e6240fc

Old Dev did not destroy the coins he bought back in Week5, and where is the 80000 coins after old Dev destroy the 250000 coins?

The following has all been implemented:

• 2 minute blocks, 12 hour diff retarget
• removal of percentage based fee, replace with a traditional fixed 0.002 WOLF fee
• a block reward of 0.48 WOLF for 17 weeks, this will produce 27417.6 WOLF (1612.8 per week)
• a block reward of 0.24 WOLF for 26 weeks, this will produce 20966.4 (806.4 per week)
• a permanent block reward of 0.12 WOLF thereafter (this will produce 20966.4 per year)

Insanity Sunday - Week 1 Results

Summary

• Total Pot: 79.52639466 BTC
• Total Acquired: 43940.88047998 WOLF
• Percentage Acquired Back: 55.25% of WOLF sold.
• Average Price: 80.98% over base (0.001809845 BTC)
• Maximum Price: 125% over base (0.00225 BTC)
• Minimum Price: 45% over base (0.00145 BTC)
• Market Activity: ~$85,000 USD (134 BTC @ $630)
• Peak Market Cap: $1,273,100 USD (((987947.27558637 /11)*10)*0.00225)*630
• Trade List: http://5.9.111.71/results/w1/trades.csv

...

Coin Destruction
Total to Destroy: 43940.88047998
destroyed: 363.36363636
destroyed: 39946.5277091
destroyed: 3630.98913454

You can see the money supply decreasing here, here, and again here

Insanity Sunday - Week 2 Results

Summary

• Total Pot: 100 BTC
• Total Acquired: 75185.33554462 WOLF
• Percentage Acquired Back: 75.185% of WOLF sold.
• Average Price: 32.74% over base (0.00132739 BTC)
• Maximum Price: 43.7% over base (0.001437 BTC)
• Minimum Price: 10% over base (0.0011 BTC)
• Trade List: http://5.9.111.71/results/w2/trades.csv

Coin Destruction
Total to Destroy: 75185.33554462 WOLF

• -6834.84868587 http://5.9.111.71:2750/block/94b1679a8e9a26637cf4f62c752d4c694a04ac3c6e0ff6ca4d3642b12345f980
• -68348.48685874 http://5.9.111.71:2750/block/e0593b35f8fc6cda3083db07618916fe3250788712c6888bc6d4c24849d130e3
• Total Destroyed: 75183.3355446 (less poloniex withdrawal fees)

Insanity Sunday - Week 3 Results

Summary

• Total Pot: 100 BTC
• Total Acquired: 83,328.15395436 WOLF
• Percentage Acquired Back: 83.328% of WOLF sold.
• Average Price: 10.052% over base (0.00110052 BTC)
• Maximum Price: 17.5% over base (0.001175 BTC)
• Minimum Price: 0% over base (0.001 BTC)
• Max Reported Profit: 62% by actively trading (others may have achieved higher)
• Trade List: http://5.9.111.71/results/w3/trades.csv

Coin Destruction
Total to Destroy: 83,328.15395436 WOLF

• -75752.8672312 http://5.9.111.71:2750/block/e1f1b5334fc8d0066b97c36fad9759550dd18f99bb19f78c62388a7b1a68680f
• -7575.19581403 http://5.9.111.71:2750/block/10361b42b6f90205cad789234a4ec8e2497042f5e499965e9e8c3d6aed0ba2e7
• -0.09090909 http://5.9.111.71:2750/block/39262801717d39a8a821689b90958f581e70dc231a72d2a02ade5af716db54d2
• Total Destroyed: 83328.15395432

Insanity Sunday - Week 4 Results

• Total Pot: 100 BTC
• Total Acquired: 82,766.1196885 WOLF
• Percentage Acquired Back: 82.76% of WOLF sold.
• Trade List: http://5.9.111.71/results/w4/trades.txt

Coin Destruction
Total to Destroy: 82,766.1196885 WOLF

• -7524.35697389 http://5.9.111.71:2750/block/11b7ddde875af34a1bc614d4073a45f13ca5dd63465d7bd11570ff5523e6011d
• -75243.569739 http://5.9.111.71:2750/block/b38f7684fb6afa1ea01ce3f99510a8b3d78ea4321db38b5bad9e344e482ff840
• Total Destroyed: 82767.9267129 (slightly too much by 1.80702439!)

Insanity Sunday - Week 5 Results

• Total Pot: 100 BTC
• Total Acquired: 73,440.58716197 WOLF
• Percentage Acquired Back: 73.44% of WOLF sold.
• Trade List: http://5.9.111.71/results/w5/trades.txt

Coin Destruction
Total to Destroy: 73,440.58716197 WOLF
pending destruction

250,000 WOLF has been destroyed in block 55e34fdb277f0d70bbac1564cf04a5db9b332c994e4150fe874f21b2efdf8de1 using transaction e5dc607e543f89d42a6162c6833621708f955cbc27847fa703e0f715284c79ff.

An additional 11 WOLF was destroyed by test transactions.

update: checkpoints at block 35000 added and main nodes updated

Thanks for the pointers! I'll attempt to add this today.

EDIT: In parser.cpp, I tried changing coinName to "/.Truckcoin/", and changing the var called "expected" to the Truckcoin magic, but I'm missing something because now it segfaults here: if(likely(0!=block->data)) {
For some reason that I can't seem to figure out, in static void findLongestChain(), gMaxBlock is null when assigned to Block *block, and then in the next if statement we dereference block, causing segfault...

I can't make much sense of this code, it seems overly complicated. Does anyone know what else I should try to get it to work?

EDIT2: Rich list seems hard to do, if it was easy then I'm sure more coins would have it by now. Without help I'll not be able to figure out how to add it, but the good news:

Block explorer is on this domain now: http://trk.cryptospread.com:2750/

Dev, can you please add it to the OP?

I don't know how, but if someone tells me I'll try to add a rich list.

https://github.com/znort987/blockparser

./blockparser/parser allBalances --limit 100

Could not agree more with this!

I agree with your point of view, and CRYPT can continue mining at present, we should consider to reduce inflation.
XC      3.33%
CRYPT 2.75%
Super  100%???WTF!!!

We should reduce to
- 1st year:  10%
- 2nd year: 5%
- 3rd and subsequent years: 1% ;

Thanks dev.

You don't need to cut PoW or cut the PoS rate. It would be greedy to do so. It would be as bad as DRK instamining then cutting the block reward. You don't want that kind of stench hanging around your coin trust me. the dev isn't here to cater to early adoptors screaming "cut the PoW". You are basically saying " I have a ton of Supercoin now, please cut the supply so my coins are worth more and I can get rich".

It doesn't work that way. If Supercoindev does cut PoW or lower the PoS rate, its an outright scam.

Supercoin is trading steady. good volume. It doesn't matter how many coins exist. The market will price the true value of Supercoin.

Bittrex do not share with user the pos coin.
so we should better have a low pos rate and keep the super pos block?

hey is this related to the way linux unzips/untars etc ?

This is new, I haven't got stuck on a fork since adding the checkpointing node.

Have you tried just to let your client do it's thing? When generating PoS blocks, they still have to be accepted by the network, so what you refer to as a fork might just be that those blocks were not all confirmed and a better block was accepted instead of yours.  If you let the client go, it should reorganize by itself and clean get back on the right fork.

repairwallet won't get you back on the correct fork. All it does is repair your wallet by removing orphans and fixing mismatched coins (transactions no accepted by the network but marked as spent in your wallet) so this steps has no influence over you getting back on the right fork.

The connection timeout issue is something I haven't had time to dig deeper in. but likely not an issue for what you are describing.  And reserve balance is only used to mark a certain amount has not available for minting.

So I really suspect that what you refer to as forking is just orphaned blocks and should normally be fixed by itself. The other thing that might be happening, is that if you generate PoS block BEFORE being fully synced to the network, you might indeed get stuck on a fork.  I'll try to get that fixed for the next release. the quick fix for that is to start your client with -reservebalance=99999999