|
lulworm (OP)
|
 |
May 23, 2016, 10:50:40 AM |
|
Guys, I will be clarifying the situation real soon so people will understand exactly whats going on.
|
|
|
|
|
|
|
|
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
d.mas
|
|
May 23, 2016, 11:32:57 AM |
|
If all of you let me have an idea for small offer and chances for Litecred community.  I'll give 10,000 LTCR. For the first 5 person, each 2,000 LTCR.  Todo:- Drop a message to each Exchanges or PM him/her, request to update LTCR Wallet on their Exchange with Litecred Wallet version 1.2.1.0: NextGen,
- Post your completed the task as a screenshot,
- Then post or drop me a PM of your LTCR address.
Note: Your wallet should use the new wallet as mention above and sync'd, instead using the old chain.I have 3 months old coins on old chain. What should I do? I was the same as you previously, but before I upgrade to the new wallet, I had backup: - Blockchain data directory
- Windows: C:\Users\MyUser\AppData\Roaming\litecred\..
- Linux: /home/myuser/.litecreed/..
- include litecred.conf
- and also wallet.dat into another directory (folder)
Then I start running the new wallet as Litecred Wallet version 1.2.1.0: NextGen until blockchain fully sync'd. I tried to mine some, and got some blocks. FYI:Under page 3 in this thread, there an info from @steve321 about downloadable Litecred blockchain data from http://cryptochainer.com/Or you may instant go to here: http://cryptochainer.com/dir/?page_id=881, and find Litecred. *** DO NOT FORGOT ALWAYS BACKUP YOUR WALLET FIRST (wallet.dat) ***As mention at the OP: OR, this steps might be more easy and fast to sync.. Let us know with your results.. Cheers! It's working and staking as well thanks man Your welcome zdeni82! Glad to know this also working for you.. |
|
|
|
|
|
lulworm (OP)
|
|
May 23, 2016, 11:49:11 AM |
|
Explorer coming up tomorrow on the new blockchain!
|
|
|
|
|
|
CryptoMaik
|
|
May 23, 2016, 02:29:55 PM |
|
Guys, I will be clarifying the situation real soon so people will understand exactly whats going on.
Okay, proceed with the necessary repairs, Good job. I have patience. |
CryptoMaik ✔
|
|
|
|
|
|
Maythe2nd
|
|
May 24, 2016, 03:12:45 PM |
|
message from yobit:
"BlackSmith LX: , already tried to update LTCR, but it stucked with new and old chain"
so is there a solution? I keep my coin in my wallet now, but I made all to change the chain, and now it's synched. |
|
|
|
|
|
d.mas
|
|
May 24, 2016, 03:55:21 PM |
|
just tried, can't open, maybe it's not running?. |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 04:30:20 PM |
|
just tried, can't open, maybe it's not running?. was restarting server. try again now! |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 04:39:30 PM |
|
just tried, can't open, maybe it's not running?. was restarting server. try again now! Let me know if it's working |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 04:43:59 PM |
|
just tried, can't open, maybe it's not running?. was restarting server. try again now! explorer is working, blockhashes the same as mine, BUT main page shows not block but tx hashes, database settings are wrong a bit sync.js was giving me lots of headache and server hosting had to suspend the server a couple of times due to over 350000 connections. I had to sync on dev machine before dumping and restoring mongodb files. wouldn't be suprise if something goes wrong somewhere but shouldn't be anything seriouse. |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 05:05:07 PM |
|
another strange thing, plenty of such shit (in many blocks) http://185.106.122.33:3001/tx/bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdcand it looks real despite empty, chain garbage ? gettransaction bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdc
{
"txid" : "bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdc",
"version" : 1,
"time" : 1464107908,
"locktime" : 0,
"vin" : [
{
"coinbase" : "03d00803",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"type" : "nonstandard"
}
},
{
"value" : 0.00000000,
"n" : 1,
"scriptPubKey" : {
"asm" : "",
"type" : "nonstandard"
}
}
],
"blockhash" : "b7f7adafe1041d7b725eb7e10a5ca2995a93f02f758504abd31e1b3581180ff7",
"confirmations" : 16
}
Yes! you are right. I guess i have to reindex the whole database on the sever itself. |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 05:15:38 PM |
|
another strange thing, plenty of such shit (in many blocks) http://185.106.122.33:3001/tx/bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdcand it looks real despite empty, chain garbage ? gettransaction bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdc
{
"txid" : "bb29f608beb6427dab85f2a27f21fa88fc2818a57bd09650477921f8fea44bdc",
"version" : 1,
"time" : 1464107908,
"locktime" : 0,
"vin" : [
{
"coinbase" : "03d00803",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"type" : "nonstandard"
}
},
{
"value" : 0.00000000,
"n" : 1,
"scriptPubKey" : {
"asm" : "",
"type" : "nonstandard"
}
}
],
"blockhash" : "b7f7adafe1041d7b725eb7e10a5ca2995a93f02f758504abd31e1b3581180ff7",
"confirmations" : 16
}
Yes! you are right. I guess i have to reindex the whole database on the sever itself. wait a minute, this shit is everywhere inside the blockchain, any wallet would give the same response. it's more serious than simple server reindexing Don't worry the problem is with the dump and restore. It's an issue with the format {json :: bson} droping the database and reindexing should fix. It's not like that with my dev explorer |
|
|
|
|
|
Stein
|
|
May 24, 2016, 05:43:43 PM |
|
So lulworm.
What is going to happen when we have coins on the old blockchain and the new one ?
This is kinda messed up
|
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 06:24:39 PM |
|
Don't worry the problem is with the dump and restore. It's an issue with the format {json :: bson}
droping the database and reindexing should fix.
It's not like that with my dev explorer
you mean everybody should reindex their chains ? or am i missing smth will reindex to redownload blockchain into mongodb database for display. |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 06:48:59 PM |
|
So lulworm.
What is going to happen when we have coins on the old blockchain and the new one ?
No one will loose their coins! Coins available before the fork are still valid and will be transferrable over the new blockchain. This is kinda messed up
A discussion took place in the old thread for over a week about a project takeover. Announcement was made and messages sent to exchanges and pool operators If theres anything you don't understand, address it here, this thread exist for a reason! |
|
|
|
|
|
|
|
Stein
|
|
May 24, 2016, 07:44:20 PM
Last edit: May 24, 2016, 08:44:41 PM by Stein |
|
A discussion took place in the old thread for over a week about a project takeover.
Announcement was made and messages sent to exchanges and pool operators
If theres anything you don't understand, address it here, this thread exist for a reason!
Well see I started mining AFTER that thread. In fact I never knew this coin existed until I saw it high up on the mining list on Yiimpool. I searched for the coin here on bitcointalk and it led me to this thread. I downloaded the wallet in this thread and started mining at home and at yiimpool/ I assumed as I do with other coins that when I mine them they will go to the proper blockchain. It's never something I worried about before. Now I have coins in the old block chain that are not on the new one and coins on the new block chain that are not on the old one. So, you see, this being a somewhat large anomloy, I came to this thread to find out why I need two block chains, because I don't code block chains and don't understand the process. That is why I came to this thread that EXISTS as you say. So, if you could please help me fix this. |
|
|
|
|
|
Stein
|
|
May 24, 2016, 08:46:54 PM |
|
once again - you cannot have both coins, only those on main chain.
this can't be "fixed", it's fundamental law of crypto.
you can only ask the dev or pool for reimbursement if they wish to pay.
but that payment will be on the main chain with new coins, wrong chain will be lost, or rather, useless
Well, damn. I have 11660 coins at this address which is on the old chain BNtWgCmsqFgHpoyYoxQiFg4TcvP16jj9dD |
|
|
|
|
|
lulworm (OP)
|
|
May 24, 2016, 10:58:18 PM |
|
I think explorer is now ok! Non standard transaction is not an error! It's just a non standard transaction the the wallet reports. http://185.106.122.33:3001/ |
|
|
|
|
|
|
|
