Topic: [ANN][XCN] Cryptonite | 1st mini-blockchain coin | M7 PoW | No Premine - page 46. (Read 578569 times)

Too much to learn  but do not have time.

Lol, I looked at the wallet now and there are two "conflicted" transactions!!

I copied the wallet file to another "Newly synchronized" client and the two conflicted transactions are there too!!

That address is mine too as I Use the faucet from time to time to ensure it's working properly.

I can give you the wallet file to check that if you need to.

The program was already synchronized before and running 24/7, Didn't resync.

As I said, It was an automated transaction Through RPC call, and I did check the faucet payouts, Previous transaction is there, proceeding transaction is there, This one is not.

Checked on both the client and blockexplorer for that address, previous payout is there as well as proceeding payout.

Well then it may actually just be that you're missing the blocks in which those transactions were included. You have to remember that when you sync with the network it will only download the most recent blocks, not the full blockchain like Bitcoin does. If you did a resync recently that may be the reason. Are you certain that the transactions weren't processed? Have you checked the actual address balances to see if the coins were sent?

Yes it should be re-included in another block essentially the same way as Bitcoin does it.

OK, but in my .conf file I only have rpc settings as payouts are automated from the website when ordered.

If the block got orphaned, shouldn't this allow the transaction to be re-included in another block? ... in the current scenario does this mean this amount will never be confirmed?

This may be a problem, That website was designed to discover such things to deal with when building bigger projects.

I believe that usually means your transaction was included in a block which got orphaned, although Tuck Fheman seemed to be having a similar issue and it turned out to be the .conf file. If you've manually added any nodes to your .conf file try removing them.

Here are transaction details


Time zone is (UTC + 2.00)

@bitfreak

I have an instruction with "!" sign in transaction list and when I hover it, I get "Conflicted" and the transactionId doesn't exist in block explorer?

Any ideas?

I am totally agreed with you on this, actually I have noted your point several pages before:
https://bitcointalksearch.org/topic/m.8878266

Even with a hard fork I'm not sure it would be possible, the schemes are just too different. And like I said on the last page there are many good reasons to implement the idea as a separate altcoin, there are always disadvantages associated with anon coins and it's no different in this case. It's better to think of these two schemes as separate concepts which both use the mini-blockchain as the backbone. It's like the difference between Bitcoin and Monero. If you've ever used Monero you'll be very aware of its weak points, and you wouldn't argue for the implementation of the Monero ring signature stuff into Bitcoin. It's the same thing in this case, it would be illogical to try to merge this anonymity scheme into Cryptonite.

A hypothetical question: suppose the author's scheme is feasibly workable and doable. Would you accept to implement it in your xcn, that means a hard fork at some point?

Struggling wrap my head  around maths

For anyone interested in the anonymity paper discussed on the last page, I recently discovered that the author has created a revised version of the paper and has posted a thread in the altcoin discussion forum where it is being discussed in more detail:

Anonymity in the Mini-Blockchain scheme

Update paper wallet design.

New files were released.
Only minor changes were made.

https://drive.google.com/open?id=0B-xG8_wDY16pbDVUUmdUd3pYUm8&authuser=1

Donations are welcome.

XCN: CX2XwA94yn2yugPkRaLKnrZx2HWc8RQMAw

Cheers!

Hi guys, need help here. My wallet seems to be stuck at block 190053 and won't proceed further. I've deleted my appdata dir and resync but it's always stuck at block 190053:

2014-12-12 18:39:29 ext-ip thread exit
2014-12-12 18:39:36 No valid UPnP IGDs found
2014-12-12 18:39:36 upnp thread exit
2014-12-12 18:40:13 receive version message: /Satoshi:0.1.1/: version 10100, blocks=200089, us=74.95.47.145:43603, them=119.81.51.10:8253, peer=119.81.51.10:8253
2014-12-12 18:40:13 Added time data, samples 2, offset +0 (+0 minutes)
2014-12-12 18:40:20 ProcessBlock: ORPHAN BLOCK, prev=0000000001f7f012019f60f9dd3c5d6b79b0fab0a548f39e6fb5bf0d442a6d8f
2014-12-12 18:40:41 receive version message: /Satoshi:0.1.1/: version 10000, blocks=200090, us=74.95.47.145:61931, them=66.45.239.67:8253, peer=66.45.239.67:8253
2014-12-12 18:40:41 Added time data, samples 3, offset -4 (+0 minutes)
2014-12-12 18:40:42 receive version message: /Satoshi:0.1.1/: version 10100, blocks=200090, us=74.95.47.145:63009, them=98.234.226.206:8253, peer=98.234.226.206:8253
2014-12-12 18:40:42 Added time data, samples 4, offset -1 (+0 minutes)
2014-12-12 18:40:42 receive version message: /Satoshi:0.1.1/: version 10100, blocks=200090, us=74.95.47.145:30012, them=0.0.0.0:0, peer=46.63.85.254:8253
2014-12-12 18:40:42 Added time data, samples 5, offset +0 (+0 minutes)
2014-12-12 18:40:42 nTimeOffset = +0  (+0 minutes)
2014-12-12 18:41:00 receive version message: /Satoshi:0.1.1/: version 10100, blocks=200090, us=74.95.47.145:40499, them=77.58.253.73:8253, peer=77.58.253.73:8253
2014-12-12 18:41:00 Added time data, samples 6, offset -1 (+0 minutes)
2014-12-12 18:41:37 ERROR: AcceptToMemoryPool: : transaction not final
2014-12-12 18:41:44 ProcessBlock: ORPHAN BLOCK, prev=000000000021ee35987d1c0515ee405e7db9b9a8dfefbd943658ad3fa8e22463
2014-12-12 18:41:50 ProcessBlock: ORPHAN BLOCK, prev=000000000021ee35987d1c0515ee405e7db9b9a8dfefbd943658ad3fa8e22463
2014-12-12 18:41:50 ProcessBlock: Orphan already exists! 0000000003dbe74b34af86d994b49721d7c61574d015583d6cb457740f38c96d
2014-12-12 18:41:58 ProcessBlock: ORPHAN BLOCK, prev=0000000003dbe74b34af86d994b49721d7c61574d015583d6cb457740f38c96d
2014-12-12 18:43:18 ProcessBlock: ORPHAN BLOCK, prev=000000000170b005b5f5950252e4187e1a495fb27ef991f354d953bc8742eedf
2014-12-12 18:43:19 ProcessBlock: ORPHAN BLOCK, prev=000000000170b005b5f5950252e4187e1a495fb27ef991f354d953bc8742eedf
2014-12-12 18:43:19 ProcessBlock: Orphan already exists! 0000000004675e89d2e3fb8d068c334a19a8f50d945d66855e3d68f59ee4a8a0
2014-12-12 18:43:36 ERROR: AcceptToMemoryPool: : transaction not final
2014-12-12 18:43:42 ProcessBlock: ORPHAN BLOCK, prev=000000000021ee35987d1c0515ee405e7db9b9a8dfefbd943658ad3fa8e22463
2014-12-12 18:43:42 ProcessBlock: Orphan already exists! 0000000003dbe74b34af86d994b49721d7c61574d015583d6cb457740f38c96d
2014-12-12 18:43:44 ProcessBlock: ORPHAN BLOCK, prev=000000000021ee35987d1c0515ee405e7db9b9a8dfefbd943658ad3fa8e22463
2014-12-12 18:43:44 ProcessBlock: Orphan already exists! 0000000003dbe74b34af86d994b49721d7c61574d015583d6cb457740f38c96d
2014-12-12 18:43:50 ERROR: AcceptToMemoryPool: : transaction not final
2014-12-12 18:43:56 ProcessBlock: ORPHAN BLOCK, prev=0000000003dbe74b34af86d994b49721d7c61574d015583d6cb457740f38c96d
2014-12-12 18:43:56 ProcessBlock: Orphan already exists! 000000000170b005b5f5950252e4187e1a495fb27ef991f354d953bc8742eedf


Any advice? Thanks!!


EDIT: nevermind, looks like same issue as Tuck Fheman was seeing...bad node:

2014-12-12 19:42:25 ERROR: ProcessBlockHeader() : AcceptBlockHeader FAILED
2014-12-12 19:42:25 Misbehaving: 66.45.239.67:8253 (0 -> 100) BAN THRESHOLD EXCEEDED
2014-12-12 19:43:12 ProcessBlock: ORPHAN BLOCK, prev=000000000378291a5c3777ae6fdb224b2fb458b424013a1a32348ec7f04f8417


Removed 66.45.239.67 from my .conf and all synced up now.

Solved it. Bad node(?).

When I couldn't sync for so long I searched this thread and popped the most posted node into the conf file and that was what started all of this "conflicted" stuff apparently. I removed that from .conf file and it sync'd finally.

Then wait for Bitfreak, He should be able to answer you

I've tried that at least 10 times with no luck. I've nuked everything except my wallet and started over and each time around block 188079 it freezes and will not go past. Transactions past 12/5 (conflicted transactions) show up, but the blocks are not sync'd. The error mentioned above appears to only happen with the original copy of my wallet and not on the backups (so far), but even the backups show the conflicted transactions from 11/29-12/5 and will not sync.

make the wallet re-download the blockchain.

Everything was working fine, up until December.  I have not been able to sync up since and have tried starting fresh repeatedly.  Around November 29th I begin getting "Status: conflicted" on transactions and then it sticks on a block (I've left it for days with no luck getting past). I then tried several backup wallets just in case, but they yielded the same results. When I go to close the client (once it's stuck on a block) I receive error messages (I'll paste an image later).

I looked for the -salvagewallet command in the console but did not see it. Is there some command I can use to attempt to salvage my wallet (if that is the issue)?