Living on the edge has its risks. Your only resolve is to convince swop management to accept your wallet.dat by email (if they will accept it), but I guess it is past the deadline now.

You are wise indeed. 

It is interesting to note that suddenly there are like 1.5PH pool miners at ninja launch for coins with no ICO/Premine. My gut feel with these ninja launches, and this is just my gut feel, is that sometimes it is the dev that hires the huge farms and are ready to press the button to get a bag of early coins to dump later. They can do this because they know exactly when to press the ninja launch button and then know exactly when to press the rig rental button. With this approach no ICO or premine are needed. Couple this with promising the moon and the starts by the newbie 1 post account and the dev will be rich (and gone) in a few days.  Who rents 1.5PH for one pool account at huge cost on a no-name coin with a newbie dev? Unless the guy is 100% assured of recovering his rental costs in a few days to make ROI + profit. In my mind there is only one person that can have this 100% assurance and that is the person that controls the OP. I am not saying this is what happened here, just that it has the potential attributes and that people need to take the possibility into account when calculating their risk appetite before investing.

If a dev has nothing to hide he will use his real BCT account for a launch.

It is up to "swap management" to decide how much they want to bend backwards on this. The point remains, no offence, that people should have foreseen the rush and stress on the chains and wallets and sent their coins a week ago to be safe. Confirmed coins in an exchange wallet means confirmed coins in an exchange wallet.

If it was allowed to send wallets in at number 99 then those people that rather gave up on their stakes to make sure coins are confirmed in the exchange wallets can cry foul and say that they could have staked up to the end and just mailed in their wallets for swop management to sort out. That is why I say rules are rules and must be strictly applied otherwise both sides of the fence can cry foul.

It is up to swop management to decide how they want to handle it but if they go to either side, then the other side will cry foul.

You should have sent your coins days ago to be safe. Leaving it to the end is your own mistake. Read my previous post.

Rules are rules and must be strictly applied else both sides of the fence will cry foul. It is not btcpool exchange or gorillastake or anyone else in the swop process to sort out peoples errors at number 99.9. With these huge number of coins and stress on the chains and wallets the issues at the end is foreseen. It can be compared to trying to get a turkey on the morning of thanksgiving - everyone will rush and fight each other. You get the turkey a week before. There are many other examples of losing out by leaving things to the end.

You guys do realize that everyone having issues at number 99 are those greedy people that wanted stakes up to the end. It is their own greed that will cause them to potentially lose their coins. Anyone with more than 2 brain cells will realise that in order for coins to be confirmed for a POS coin there needs to be coins staking somewhere. If everyone moves their coins just before the end, where will there be coins that are staking for the confirms? Unless there are coins somewhere at btcpool exchange or Gorillastake or some other place that qualifies for the swop that have set their coins open for staking with a maturity of >24 hours, the coins at the end will not be able to confirm.

There will be people that lose their coins that got overwhelmed with their greed for staking and it will be those people that scream scam, thief etc. People had weeks to move their coins and their affairs in order for the swop. People's greed will never end especially in crypto and it amazes me how it has been proved again here with this swop.

Fixed 

Urrrgh. Dev your git looks messy. Please sort it out.

Dev you have files missing in your /src/zerocoin folder. Looks like the files after "P" in the alphabet. Can you please copy those from where you copied the source and complete the git? Files missing are:

Params.cpp
Params.h
SerialNumberSignatureOfKnowledge.cpp
SerialNumberSignatureOfKnowledge.h
SpendMetaData.cpp
SpendMetaData.h
Zerotest.cpp
Zerotest.h
Zerocoin.h

While fixing the code, perhaps add 2 zeros to max coin. Last when I looked at the source earlier today it was at 300,000.

It depends if they were mined on the correct fork. All coins mined on an incorrect fork will have been wasted hash and the coins lost as there will be no accounting entry on the correct block chain crediting you with the coins. All coins mined on the correct fork but sent on an incorrect fork will still exist on the correct fork. As soon as the fork is corrected those coins will be back.

Read this and then I hope you understand the principle. https://bitcointalk.org/index.php?topic=1040090.msg11244483#msg11244483

Dev is back. Nice 

Looks like you guys are struggling with the syncing. I made a new bootstrap.dat file up to block 6447. The link is in the post with the Raspberry Pi instructions. There is also a untarred version to make it easy for the Windows users. Just copy the bootstrap.dat file into directory where your wallet file is and run the wallet client.

https://bitcointalk.org/index.php?topic=1040090.msg11238640#msg11238640

I asked the dev some questions 2 days ago in PM that I would like explanations for. I think the questions scared him off and he has bailed by the look of things.

Dev can you just check whats going to happen when money supply hits 300,000 and if coins after that will be accepted?
If POW will stop at 3600 and not continue giving 90 coins
If the chain will get stuck or otherwise only give 36 coins for blocks  3600 and 4100

Also update OP with rest of the stats:

Block time : 60s
Min stake age : 6 hours?
Max stake age : Unlimited?
Number of confirmations

It is an interesting dynamic to have a constant POS reward of 36 coins in perpetuity instead of an interest %.

Raspberry Pi wallets updated to v1.2.0.0 including checksums.

1) All download links as well as the installation script stay the same
2) If you previously ran the installation script you can just download the new daemon and Qt binaries directly and overwrite the binaries in ~/opt/megastake

Don't think about coins sent as actual coins being sent. Think about it as an accounting entry into the public ledger that is not limited to a specific location, company or person. Any entry into the true and correct ledger (correct block chain) is there for any compatible application (exchange wallet in this case) to interpret and display. If you sent coins, the entry into the ledger has been made. As soon as whichever party in question upgrades their blockchain interpreter (wallet) so that it can read the block chain and know how many coins are assigned to each address at the current block height, the coins will be displayed at the destination address in their wallet.

You are right. It comes down to dev action / non-action eg. creating a roadmap, proper block explorer etc.. A dev makes or breaks his own coin. Lets hope that this dev gets it and if we ever see the dev in here again, that he comes to the party.

Here are Raspberry Pi wallets for v1.2.0.0 - both the Qt and the headless daemon.

Important:
1) The wallet was built on a Raspberry Pi2 (ARM7) running Raspbian. It might work on an older Pi but I have not tested it
2) Installation directory where the binaries are installed is ~/opt/megastake or /home/pi/opt/megastake
3) All that is needed is to execute the command below on your Pi in a terminal window and afterwards you click on the Megastake icon on the desktop
4) An Internet connection is required for the installation
5) A bootstrap.dat is used to fast track the blockchain sync - up to block 6447
6) You need at least an 8GB memory card
7) The installation itself takes about 30-45min and the loading of the blockchain (once-off) another few minutes since it is still small
8.)You cannot just download the binaries, you have to run the script to get the dependencies as well else it will not run
9) The installation script does not enable the UFW firewall by default. If you want to enable it, uncomment the UFW lines in the script and add the port you want open and run it again or enable it manually by running the UFW commands as in the script with the correct port numbers.
10) Upon the first time startup of the Qt wallet, the Megastake splash screen will appear for a few minutes while the blockchain is imported. The progress is not readable against the black background. Give it time and the splash screen will disappear and the wallet will open up.
11) Always backup your wallet first.

Let me know about any issues that you may encounter.

To kickstart the installation execute the following command at the command prompt or in a terminal window on your Pi:

Direct links:
Link to installation script
Link to megastake-qt
Link to megastaked
Link to bootstrap.dat up to block 6447
Link to bootstrap.dat up to block 6447, untarred for the Win users
Link to checksums.txt

If you like this, you are welcome to donate XMS to RA98biHDqpjvdQy65E2FKh3zwkShCLZkxz

Quite an anticlimax.