Pages:
Author

Topic: plz delete - page 3. (Read 12667 times)

legendary
Activity: 1638
Merit: 1013
July 03, 2015, 11:50:34 PM
Not true, just detach database at shutdown from a synced node to get transferable blk .dat files

What I said is the truth and I also did say what you just posted that you can detach the database and copy the blk file but that imo it is a more complex process. My issue was that the normal way of doing a bootstrap.dat is not working. I have not appetite to dig in the past here and fight about things that is not relevant anymore because Ecash is screwed anyways.
sr. member
Activity: 440
Merit: 250
July 03, 2015, 07:47:01 PM
Hey spots. Your holding some ecash I think. What do you think we should do?
The high staking rate we voted on months ago seems to have caused a mess.


For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.


The last known block that everyone agrees on then host a node from that block onwards.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.

Not true, just detach database at shutdown from a synced node to get transferable blk .dat files
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
July 03, 2015, 04:15:14 PM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.


The last known block that everyone agrees on then host a node from that block onwards.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.

Not true, just detach database at shutdown from a synced node to get transferable blk .dat files
legendary
Activity: 1638
Merit: 1013
July 03, 2015, 06:56:18 AM
Glad to hear that someone was even trying to fix this coin. Thanks. What do you mean "Choose or create a new wallet". Is there a template we can use? Sounds like a big project. How many people do you think are still holding ecash?

Due to the issues with your current chain and the high number of coins in circulation, it does not make sense to work on the existing wallet and chain. You must therefore either code a new wallet or copy one. Coding a new wallet is possible but does not make sense due to the effort involved. Your best bet would be to do what all the scam devs do, take an existing wallet of anther coin, change the coin specs to what you want it to be, find and replace the name to the name you want, replace the graphics and put a premine in the first block. Then swop the new coins for the old. You need to get someone with coding and wallet experience to do this for you and while you are looking for a new wallet, you can just as well choose one with some features that you deem to be adding value.
sr. member
Activity: 440
Merit: 250
July 03, 2015, 06:15:42 AM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.


The last known block that everyone agrees on then host a node from that block onwards.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.

Glad to hear that someone was even trying to fix this coin. Thanks. What do you mean "Choose or create a new wallet". Is there a template we can use? Sounds like a big project. How many people do you think are still holding ecash?
legendary
Activity: 1638
Merit: 1013
July 03, 2015, 05:30:23 AM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.


The last known block that everyone agrees on then host a node from that block onwards.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.
legendary
Activity: 1218
Merit: 1001
July 03, 2015, 05:15:37 AM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.


The last known block that everyone agrees on then host a node from that block onwards.
sr. member
Activity: 440
Merit: 250
July 02, 2015, 10:31:52 AM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.
sr. member
Activity: 440
Merit: 250
July 01, 2015, 05:43:29 AM
For now we need to get some active connections. Is hosting a nodes what needs to happen?

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.
byk
newbie
Activity: 34
Merit: 0
June 28, 2015, 01:42:30 PM
OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.
member
Activity: 118
Merit: 10
June 28, 2015, 01:34:42 PM
He is going to be super busy with the coin swap.  I think we should wait and not bother him right now. 
byk
newbie
Activity: 34
Merit: 0
June 28, 2015, 01:28:56 PM
This doesn't work again.
Let's ask Spots to take over this coin, to be the dev of new one, to stop this silly rate, make a swap with a ratio 1:1 000 000 and the coin will be on market again.
What do you say? Let's vote on that.
member
Activity: 118
Merit: 10
June 28, 2015, 11:47:30 AM
Not completely dead, but on life support.  I received a couple of blocks today.  I just like messing around with this coin.
member
Activity: 118
Merit: 10
June 28, 2015, 09:18:02 AM
Anyone know how to host a node?
sr. member
Activity: 440
Merit: 250
June 27, 2015, 07:04:45 PM
No connections? Sounds like a few of us are online why would there be no active connections?
I am also dead.


Mine is dead for the last 90 min.
byk
newbie
Activity: 34
Merit: 0
June 27, 2015, 04:26:10 PM
Mine is dead for the last 90 min.
member
Activity: 118
Merit: 10
June 27, 2015, 03:37:46 PM
Macro recorder is pretty cool.  Does anyone have any connections? I seem to have lost mine this morning.
newbie
Activity: 16
Merit: 0
June 26, 2015, 06:25:13 PM
Sounds good to me. Still confused on how the swap works.

Like I said I got my wallet synced up finally.
It is starting to stake now but it is negative stake amounts. I think someone else had the same problem. How did you fix it?

Oh yea. We are at 1178081

Makes total sense..LOL

I never managed to fix the negative staking issue. I did kind of fix the problem though.
I started with a new wallet on a spare laptop, let it sync (which was luckily no issue), then transferred all coins to the new wallet. Had to send coins at a maximum of 500000000.00 at a time otherwise it crashed. Now wallet stakes more than it negative stakes, which is fine by me.

Also, I have had the same problem as others, wallet stops staking. To solve the issue, create a new address & send coins to yourself, seems to restart the staking process after the hour for coin maturity. Do this every day or so.

Hope this helps someone  Smiley
sr. member
Activity: 440
Merit: 250
June 26, 2015, 12:01:36 PM
Gravy. Used jitbit macro recorder. jitbit.com/macro-recorder.

Just start recording / click on ecash wallet link to open / let wallet load and grab blocks / wait a few seconds and close wallet / stop recording.

Go to the menu and set the amount of times you want it to play over in "special play"


Was the Macro recorder easy to setup? I am about 17,000 blocks behind.  I get the negative stakes every once in a while, but they seem to be more frequent lately. I do not have a clue as how to fix it.
member
Activity: 118
Merit: 10
June 26, 2015, 10:06:58 AM
Was the Macro recorder easy to setup? I am about 17,000 blocks behind.  I get the negative stakes every once in a while, but they seem to be more frequent lately. I do not have a clue as how to fix it.
Pages:
Jump to: