[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS

[ebite]

It's built to solve the biggest problem with current crypto-currencies, a lack of purchase motivation.

It seems people lack of purchase of XCR right now.

[luckygenough56]

I would say it's rather a lack of Windows wallet right now 

[matrix961]

I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.

The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.

https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc

[luckygenough56]

Where i'm supposed to put that blockchain ?

[mydearvoice]

Looking forward to the arrival of the Windows wallet

[informer]

Where i'm supposed to put that blockchain ?

If you trust it you can place it in your root directory and overwrite the current one. Personally, I'm waiting for 0.1.6. It will be probably be released today or tomorrow.

informer

[Sammie Sna]

Oh.the price is so low and i don't have money to buy more.....What i can do..!!

[informer]

Crypti mentioned in Cryptomen Weekly report:

http://cryptomen.com/2014/08/cryptomen-weekly-report-august-27-2014/

informer

[Litoshi]

I sent .2 BTC from Coinbase to Cryptsy yesterday, ( 1 months worth of faucet BTC) and after 10 hours it still did not show.  Now this AM, I see this on Cryptsy:

Deposits delayed

Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.

[Litoshi]

Oh.the price is so low and i don't have money to buy more.....What i can do..!!

Get some BTC from faucets:

Link is below

[schmelix]

I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.

The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.

https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc

Thanks!

But my nodes are still not able to sync since 1,5 hours

[matrix961]

I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.

The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.

https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc

Thanks!

But my nodes are still not able to sync since 1,5 hours

Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.

[informer]

I sent .2 BTC from Coinbase to Cryptsy yesterday, ( 1 months worth of faucet BTC) and after 10 hours it still did not show.  Now this AM, I see this on Cryptsy:

Deposits delayed

Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.

Yeah I saw that yesterday. Strange thing is that I sent .1 to cryptsy from my BTC wallet and it went through in no time flat. so, it may be an exchange issue.

informer

[Litoshi]

I sent .2 BTC from Coinbase to Cryptsy yesterday, ( 1 months worth of faucet BTC) and after 10 hours it still did not show.  Now this AM, I see this on Cryptsy:

Deposits delayed

Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.

Yeah I saw that yesterday. Strange thing is that I sent .1 to cryptsy from my BTC wallet and it went through in no time flat. so, it may be an exchange issue.

informer

I checked the blockchain while waiting for it to go thru... took 12 hours to get 90 confirms.  Usually i see the BTC at Cryptsy after 70 confirms. 

[l3n1nN]

Looks like Crypti is going to be added to Mintpal v2. Would definitely be great news if the windows wallet was out by then. TY Crypti Dev.

[canej]

I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.

The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.

https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc

Thanks!

But my nodes are still not able to sync since 1,5 hours

Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.

Just tried it and works!

Hooray!!!!!!

Pitty that the dev's couldn't even help here!

Here is a check list to help you :-

1. Make sure delete logs.log file and blockchain.db then copy the downloaded one above into your home folder (where the previous block chain was.)
2. Make sure you have port forwarding enabled for port 6040 this is key.
3. takes about 45min to get all going. Easiest way to monitor this is check your CPU usage you will see it increases over 50% when you first kick of the process.
4. The current .db is using about 4.5GB of memory now. So you need to have that amount free. I have 6gb so going to have to increase mine soon. Really hope 1.6 will fix such heavy RAM usage. This coin WILL fail if they cant address this. DEVs take note this has to work in the next release.

Thank you again for posting the DB. IF .1.6 is not out tomorrow will update an updated db tomorrow.



 

[Wulfcastle]

Pitty that the dev's couldn't even help here!

Such "help" is NOT appreciated in crypto...  the devs did the right thing!   

...0.1.6 is just around the corner...

@Devs

Any update on 0.1.6?

[Litoshi]

I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.

The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.

https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc

Thanks!

But my nodes are still not able to sync since 1,5 hours

Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.

Just tried it and works!

Hooray!!!!!!

Pitty that the dev's couldn't even help here!

Here is a check list to help you :-

1. Make sure delete logs.log file and blockchain.db then copy the downloaded one above into your home folder (where the previous block chain was.)
2. Make sure you have port forwarding enabled for port 6040 this is key.
3. takes about 45min to get all going. Easiest way to monitor this is check your CPU usage you will see it increases over 50% when you first kick of the process.
4. The current .db is using about 4.5GB of memory now. So you need to have that amount free. I have 6gb so going to have to increase mine soon. Really hope 1.6 will fix such heavy RAM usage. This coin WILL fail if they cant address this. DEVs take note this has to work in the next release.

Thank you again for posting the DB. IF .1.6 is not out tomorrow will update an updated db tomorrow.

Crypti can only succeed if it has community support.  This includes helpful information like this, as well as responding to concerns and questions from new members and investors.

Keep up the good work, canej

[matrix961]

Yep the community helps each other out while the devs focus on fixes. I know the devs are working hard and they have been doing a great job.

[canej]

Pitty that the dev's couldn't even help here!

Such "help" is NOT appreciated in crypto...  the devs did the right thing!   

...0.1.6 is just around the corner...

This has been a common issue, providing a db for us to sync with from trusted source like the devs would have saved me many days of trying different things.

So my moan was that dev's should also help keep things running instead of just focusing on new features. Uploading a fresh .db does not even take 5 mins. But to sync from scratch has taken me nearly 2 days.

Its great someone did upload a db to help sync issues. Looking forward to new client as have spent way too much time just trying to get client to work. Even Sys dev's helped users out with issues and provided fixes in a few days.... Its been weeks now we have been waiting for 0.1.6...