Neither Dice nor Lottery are producing results

[pc]

Is the coin dead?

Yes: https://bitsharestalk.org/index.php?topic=8916.msg127027#msg127027

[kanes]

Is the coin dead?

[bitmeat]

The PoW was merged mining anyways

[barwizi]

I forked the lotto part and have integrated it into NoirShares. The first issue I'll point out is that after perusing LTS code, I have not seen anything that points to key theft.

Second, I think for a failed attempt this was good. I intend to keep trying on my fork. He has already done most of the work and pointed out the issues so if someone was really interested, they could continue the LTS chain.

Not sure if I am on the right track but I've already begun discussing ways around the forking issues. Since NRS already uses a seperate random seeding method to randomize PoW , perhaps it can work dual purpose and maybe function with the lotto.

I say let Freetrade go and focus on something else, people love to point at him in a dark light but has anyone ever really considered the amount of innovation he does? I follow his work, I can tell you , he does not deserve any of this negativity.

And on that note, I see no reason why a developer must be tied to a project, if they feel they should move on , it is their choice. Apart from the PoW, keep in mind that these were basically free shares.

[CLains]

My view is that dev talent is scare and best redirected away from failed projects rather than throwing new effort at it.

I tried my best and ultimately failed.

What is more scarce than dev talent is groups of talented devs working together with an eye for future scaling and economic viability. There are plenty of rewarding projects if you move forward, learn DPoS and aim for Virginia Tech.. 

[Riverhead]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Look, it's not a true 2-factor, unless it uses a separate device to decrypt.

I don't think FT has stolen keys,

Sorry for the rant, but this is disaster in the makings. I hope I'm wrong, I really do.

Agree on all points. Referring to it as 2FA was incorrect.




Sent from my SM-G900T using Tapatalk

[liondani]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Look, it's not a true 2-factor, unless it uses a separate device to decrypt. If there is a key-logger, it doesn't matter how strong your second password on top of the private key is. This is true for all crypto projects. It's scary full of amateur decisions.

Even the "non-hobby" projects like DNS and BTSX have that flaw. And as I mentioned a billion times, it is extremely easy to fix. Heck even Bytemaster mentioned somewhere he added it to the toolkit as method somewhere, but nobody is using it.

I don't think FT has stolen keys, if he did, he'd have more than just personal issues.

However in this day and age you can NEVER be sure what's running on your desktop. Given that it's a huge incentive, you know someone, somewhere will exploit the attack vector.

I would not import any keys until this issue is resolved. And I say that even for the existing DACs.

Sorry for the rant, but this is disaster in the makings. I hope I'm wrong, I really do.

 

[bitmeat]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Look, it's not a true 2-factor, unless it uses a separate device to decrypt. If there is a key-logger, it doesn't matter how strong your second password on top of the private key is. This is true for all crypto projects. It's scary full of amateur decisions.

Even the "non-hobby" projects like DNS and BTSX have that flaw. And as I mentioned a billion times, it is extremely easy to fix. Heck even Bytemaster mentioned somewhere he added it to the toolkit as method somewhere, but nobody is using it.

I don't think FT has stolen keys, if he did, he'd have more than just personal issues.

However in this day and age you can NEVER be sure what's running on your desktop. Given that it's a huge incentive, you know someone, somewhere will exploit the attack vector.

I would not import any keys until this issue is resolved. And I say that even for the existing DACs.

Sorry for the rant, but this is disaster in the makings. I hope I'm wrong, I really do.

[biophil]

Has anybody made some kind of best-practices manual for claiming stakes in new DACs? There are a couple no-brainer things one could do, such as moving your PTS to a new address after every snapshot (and certainly before importing PTS keys), keeping your AGS donation wallets locked at all times (i.e., never use those wallets for BTC or PTS transactions), etc. Has anybody already written up such guidelines?

Oh, another thing: immediately after importing AGS, move your newly-claimed shares to a completely different wallet.dat file; that way your AGS key is not permanently in your LTS wallet.dat file.

[biophil]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Naturally with a compromised wallet they get the plane text version. However if you imported your keys into a non compromised wallet a developer is no further ahead of anyone else who has just a locked .dat file. They'd still need to get you to install and unlock a compromised wallet to get the keys in plane text. Try dumping your private keys in a QT wallet with it locked. Doesn't work.

As far as needing a mechanism to claim AGS without a plane text key import it seems that's on each DAC developer to implement but from what Toast said the expensive part is getting it audited because otherwise you're still just trusting the developer.

I learned something new here.
So using lts as a example
I dumped my  un encrypted text based ags key from the wallet I made my donation from into the lts wallet.
In order to access  the ags donation wallet they would need the password for the ags donation wallet and the private key?

No, all they need is the private key. Your AGS key is now in two places: your AGS wallet.dat, and the LTS wallet.dat. If your LTS wallet is encrypted with a strong passphrase, then you're good. If you imported your AGS key into the LTS wallet without encrypting the LTS, then your AGS is wide open and exposed to anybody with access to your computer.

[Gentso1]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Naturally with a compromised wallet they get the plane text version. However if you imported your keys into a non compromised wallet a developer is no further ahead of anyone else who has just a locked .dat file. They'd still need to get you to install and unlock a compromised wallet to get the keys in plane text. Try dumping your private keys in a QT wallet with it locked. Doesn't work.

As far as needing a mechanism to claim AGS without a plane text key import it seems that's on each DAC developer to implement but from what Toast said the expensive part is getting it audited because otherwise you're still just trusting the developer.

I learned something new here.
So using lts as a example
I dumped my  un encrypted text based ags key from the wallet I made my donation from into the lts wallet.
In order to access  the ags donation wallet they would need the password for the ags donation wallet and the private key?

[Riverhead]

Keep in mind a non compromised wallet stores an ENCRYPTED copy of your private keys. That's why you need to unlock your wallet with a good passphrase. It's effectively 2-Factor Authentication. They need both the .dat file AND your pass phrase for it to be useful.

Naturally with a compromised wallet they get the plane text version. However if you imported your keys into a non compromised wallet a developer is no further ahead of anyone else who has just a locked .dat file. They'd still need to get you to install and unlock a compromised wallet to get the keys in plane text. Try dumping your private keys in a QT wallet with it locked. Doesn't work.

As far as needing a mechanism to claim AGS without a plane text key import it seems that's on each DAC developer to implement but from what Toast said the expensive part is getting it audited because otherwise you're still just trusting the developer.

[Gentso1]

Better to try and fail then to never try in the first place, thanks for the fun.

Any insight into the next project?

That is very counter intuitive statement... read my posts in this sub-forum... how could this project be a success?

Now back to the priv keys of mine that I imported... they are forever in jeopardy of someone deciding that stealing/using them is the better way to go...

On that note - Is not this easy enough to transfer the AGS donations from the original 'donation from' to a new one?

Your keys aren't "out there" unless this client was compromised and I don't think it was. A malicious dev can't somehow get your private keys unless they release a compromised version and you open your wallet.dat with it and unlock it.

Good to know Riverhead!
 I imported just a few keys but still prefer not to give my AGS to somebody for no reason at all...

maybe I am wrong but when any of us input our private key (ags, pts, whatever) anyone who has that key can claim to be the owner of said address. Now in wallets anyone who has that private key has complete access to said wallet. So for a pts wallet for example  if you think your key is compromised you simply transfer your pts to a new wallet with a new addy and you have a new private key that you can use to claim your stake.

With ags it goes by the addy the donation came from. So their is no way to substitute another addy unless it is manually done in the genesis block of every new DAC(like what they did with some of the keyID addys).

I for one should have known better and just not imported my private ags key and just "passed" on what ever lts had to offer, its just to much risk if a dev is bad intentions. This isn't anything against FT but any dev.  We want a trust less system but the irony is with ags we have to trust every dev for every DAC as the only way to currently claim shares. keyID, LTS, what about the music one or vote, how about PLAY. We must have another option for ags holders to claim shares other then private keys or simply not support DACS that will not implement another method. As more devs start becoming interested in the bitshares toolkit we have more player's in the game and it only takes one to have bad intentions. Lets be pro active instead of reactive. 

[Riverhead]

Your keys aren't "out there" unless this client was compromised and I don't think it was. A malicious dev can't somehow get your private keys unless they release a compromised version and you open your wallet.dat with it and unlock it.

That makes perfect sense.

I forgot the wallet.dat itself is encrypted. The client still could have been compromised when the keys were actually imported though, right?

Yes. The client knows your private key at import and could, in theory, encrypt the plain text key with a public key they own and send it to themselves. The destination would then have a script decrypt the private key, import it into a burner wallet and transfer the money. It would all be over in seconds.

[merockstar]

Your keys aren't "out there" unless this client was compromised and I don't think it was. A malicious dev can't somehow get your private keys unless they release a compromised version and you open your wallet.dat with it and unlock it.

That makes perfect sense.

I forgot the wallet.dat itself is encrypted. The client still could have been compromised when the keys were actually imported though, right?

[Riverhead]

Good to know Riverhead!
 I imported just a few keys but still prefer not to give my AGS to somebody for no reason at all...

Agreed. Unless that someone is me haha

[tonyk]

Better to try and fail then to never try in the first place, thanks for the fun.

Any insight into the next project?

That is very counter intuitive statement... read my posts in this sub-forum... how could this project be a success?

Now back to the priv keys of mine that I imported... they are forever in jeopardy of someone deciding that stealing/using them is the better way to go...

On that note - Is not this easy enough to transfer the AGS donations from the original 'donation from' to a new one?

Your keys aren't "out there" unless this client was compromised and I don't think it was. A malicious dev can't somehow get your private keys unless they release a compromised version and you open your wallet.dat with it and unlock it.

Good to know Riverhead!
 I imported just a few keys but still prefer not to give my AGS to somebody for no reason at all...

[Riverhead]

Better to try and fail then to never try in the first place, thanks for the fun.

Any insight into the next project?

That is very counter intuitive statement... read my posts in this sub-forum... how could this project be a success?

Now back to the priv keys of mine that I imported... they are forever in jeopardy of someone deciding that stealing/using them is the better way to go...

On that note - Is not this easy enough to transfer the AGS donations from the original 'donation from' to a new one?

Your keys aren't "out there" unless this client was compromised and I don't think it was. A malicious dev can't somehow get your private keys unless they release a compromised version and you open your wallet.dat with it and unlock it.

[tonyk]

Better to try and fail then to never try in the first place, thanks for the fun.

Any insight into the next project?

That is very counter intuitive statement... read my posts in this sub-forum... how could this project be a success?

Now back to the priv keys of mine that I imported... they are forever in jeopardy of someone deciding that stealing/using them is the better way to go...

On that note - Is not this easy enough to transfer the AGS donations from the original 'donation from address' to a new address?

[Brekyrself]

I am curious if the dev fund of lts was left alone or liquidated before this announcement, also the time seems odd as its right before ags/pts share's mature...

Care to comment on how much of the dev fund was cashed out before your announcement freetrade?

Sure. 0.

I was interested in building a successful project, not cashing out a few pennies. My view is that dev talent is scare and best redirected away from failed projects rather than throwing new effort at it.

I tried my best and ultimately failed. I can understand why participants might be disappointed, as am I, but personal attacks are unwarranted where hugely ambitious, hugely risky projects fail. I've risked more and lost more than anyone else with this project.

Better to try and fail then to never try in the first place, thanks for the fun.

Any insight into the next project?

[merockstar]

lottoshares was an ameteur/hobby product, but that's ok. Who was expecting massive ROI and widespread adoption?


Part of the value of AGS is that it filters out winners and value producers. Don't feel "ripped off", feel vindicated.

I don't feel ripped off by any means. Had the project worked out it very well could have ROI'd and had wider adoption imo.

I was just concerned about my AGS private keys is all. But I'll feel a lot better if FreeTrade keeps responding to this thread.

[toast]

lottoshares was an ameteur/hobby product, but that's ok. Who was expecting massive ROI and widespread adoption?


Part of the value of AGS is that it filters out winners and value producers. Don't feel "ripped off", feel vindicated.

[merockstar]

Don't panic. There is only the possibility of keys being compromised. Did you use the Windows binary or build from source? Anyway, FT had good intentions to do this project but has abandoned it for whatever reason. That doesn't mean a trojan key stealer was in the code.

If this was a DAC from someone completely unknown it might be worrisome. I say if yu still have your AGS DNS and after a time Notes you're in the clear because I doubt someone with all the AGS keys would wait around.

I built from source.

FreeTrade: thanks for trying to a create a DAC. sorry it didn't work out.

You have to admit though, as an AGS holder who imported his private keys, it's scary as fuck to see the whole project end so abruptly. Right before people's AGS and PTS airdrops are about to mature. And I kind of feel like your (FT's) rep is solid enough to have long con level of trust, but not so ingratiated that it isn't a disposable identity. It would certainly be tempting, and if it were a scam, this is probably how it would play out. No? Also I saw this thread at 730am, so I panicked easier.

It's reassuring to still see you here communicating though.

EDIT: I hope you don't take what I'm trying to say the wrong way. It sucks to be second guessing yourself after you've decided to place trust in somebody.

[FreeTrade]

I would hardly view asking a question as a personal attack but if you took it that way I am sorry.

Sorry, no I didn't view your comments as an attack - that was a fair question.

My other comments are better understood as a general response to other participants screaming scam, trojan, dodgy rep, abandonment, etc.  I should have made a separate post for them.
     

[Gentso1]

I am curious if the dev fund of lts was left alone or liquidated before this announcement, also the time seems odd as its right before ags/pts share's mature...

Care to comment on how much of the dev fund was cashed out before your announcement freetrade?

Sure. 0.

I was interested in building a successful project, not cashing out a few pennies. My view is that dev talent is scare and best redirected away from failed projects rather than throwing new effort at it.

I tried my best and ultimately failed. I can understand why participants might be disappointed, as am I, but personal attacks are unwarranted where hugely ambitious, hugely risky projects fail. I've risked more and lost more than anyone else with this project.

I would hardly view asking a question as a personal attack but if you took it that way I am sorry. If you look at the situation objectively, I would hope you can agree that some questions needed to be asked.

I agree that dev talent is very very scarce but the situation highlighted the need for a claiming method other then ags private keys. I had no real stake in LTS and I also understand the words experimental. Thanks for taking the 2 mins to address the concerns of shareholders. Lets call this a dead issue and hopefully we as users have learned something and you as devs will understand that a change must be made.

[Riverhead]

Interesting. So since Zhangweis is deep into Just Dice Style DAC I wonder what his take is on this. I'll point him to this thread for comment about claiming without inputting private key.

[FreeTrade]

I am curious if the dev fund of lts was left alone or liquidated before this announcement, also the time seems odd as its right before ags/pts share's mature...

Care to comment on how much of the dev fund was cashed out before your announcement freetrade?

Sure. 0.

I was interested in building a successful project, not cashing out a few pennies. My view is that dev talent is scare and best redirected away from failed projects rather than throwing new effort at it.

I tried my best and ultimately failed. I can understand why participants might be disappointed, as am I, but personal attacks are unwarranted where hugely ambitious, hugely risky projects fail. I've risked more and lost more than anyone else with this project.

[Gentso1]

It would be tough because a likely code hack like that would be in the binaries and not checked into GitHub (reason md5 is so important).

Also I can't comment on how ags is stored but since claiming requires a private key i3 doesn't have I doubt anything can be done. Only future snapshots would benefit and since ags snapshot is long in the books....

Maybe I am misunderstanding you. I am worried about anyone who trusted this software or dev with their ags private key.If FT has the private keys of many users who had to use them to claim LTS, it would be a race to claim future DAC's. I don't really care about lts, I didn't have any stake in it other then my ags donation. I am concerned about FT having access to private keys via LTS claiming and his work on future projects.

I hear ya. What I'm saying is the ags private keys are set. Since pts is liquid they can be moved to new keys for future snapshots (like music on the 10th) but any previous snapshots (DNS, BTSX) are cast in stone now so best to claim and move to new keys their respective blockchains so if private keys are compromised the addresses are empty.

I don't think there is anything that can be done for ags holders. However I really doubt the keys are compromised. FT has his issues but I don't believe he'd pull off a massive heist.

I got ya. Yea I understand how the ags keys work and I don't really think this is a setup for the next DAC and he is going to go on this huge claiming spree. I do think all the info pointed out early casts a bit a a shadow on FT, and his past was semi shadowed with he memory coin history( which tbh I never fully understood even after reading much of the orginal thread on BCT).The immediate shutdown of the lts forum without even a message.   

Anyways their is no reason to beat a dead horse. As users and shareholders we should now make a clear DEMAND to stop the use of private keys to claim one's stake. Every DAC that's created. We can all start by asking "how will I have to claim my stake" in the thread of every DAC to send a clear message.     

[Riverhead]

If you're looking for a DAC to take your mind off LTS then Zhangweis' JDS is looking for testers

https://bitsharestalk.org/index.php?topic=9758

[Riverhead]

Don't panic. There is only the possibility of keys being compromised. Did you use the Windows binary or build from source? Anyway, FT had good intentions to do this project but has abandoned it for whatever reason. That doesn't mean a trojan key stealer was in the code.

If this was a DAC from someone completely unknown it might be worrisome. I say if yu still have your AGS DNS and after a time Notes you're in the clear because I doubt someone with all the AGS keys would wait around.

[merockstar]

shit.

I waited so long to claim LTS because I was worried about giving up my private keys.

finally I did it after the first bubble.

shit...

[Riverhead]

It would be tough because a likely code hack like that would be in the binaries and not checked into GitHub (reason md5 is so important).

Also I can't comment on how ags is stored but since claiming requires a private key i3 doesn't have I doubt anything can be done. Only future snapshots would benefit and since ags snapshot is long in the books....

Maybe I am misunderstanding you. I am worried about anyone who trusted this software or dev with their ags private key.If FT has the private keys of many users who had to use them to claim LTS, it would be a race to claim future DAC's. I don't really care about lts, I didn't have any stake in it other then my ags donation. I am concerned about FT having access to private keys via LTS claiming and his work on future projects.

I hear ya. What I'm saying is the ags private keys are set. Since pts is liquid they can be moved to new keys for future snapshots (like music on the 10th) but any previous snapshots (DNS, BTSX) are cast in stone now so best to claim and move to new keys their respective blockchains so if private keys are compromised the addresses are empty.

I don't think there is anything that can be done for ags holders. However I really doubt the keys are compromised. FT has his issues but I don't believe he'd pull off a massive heist.

[Gentso1]

It would be tough because a likely code hack like that would be in the binaries and not checked into GitHub (reason md5 is so important).

Also I can't comment on how ags is stored but since claiming requires a private key i3 doesn't have I doubt anything can be done. Only future snapshots would benefit and since ags snapshot is long in the books....

Maybe I am misunderstanding you. I am worried about anyone who trusted this software or dev with their ags private key.If FT has the private keys of many users who had to use them to claim LTS, it would be a race to claim future DAC's. I don't really care about lts, I didn't have any stake in it other then my ags donation. I am concerned about FT having access to private keys via LTS claiming and his work on future projects. 

[liondani]

None of the devs have built such a tool yet because we trust ourselves. It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

No one is questioning you. However I prefer to sign on a machine that is offline. Produce the signature there. Then transfer via USB and then import it. This is the safest.

Even if your software is trusted most people's machines aren't!

With AGS not being liquid this is a big deal.

And I beg you to add this to the code it is relatively easy to do. And should have been the default way to import keys in the toolkit.

Going forward this is a must for BTS DACs

 

[GaltReport]

None of the devs have built such a tool yet because we trust ourselves. It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

No one is questioning you. However I prefer to sign on a machine that is offline. Produce the signature there. Then transfer via USB and then import it. This is the safest.

Even if your software is trusted most people's machines aren't!

With AGS not being liquid this is a big deal.

And I beg you to add this to the code it is relatively easy to do. And should have been the default way to import keys in the toolkit.

Going forward this is a must for BTS DACs

 

[bitmeat]

None of the devs have built such a tool yet because we trust ourselves. It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

No one is questioning you. However I prefer to sign on a machine that is offline. Produce the signature there. Then transfer via USB and then import it. This is the safest.

Even if your software is trusted most people's machines aren't!

With AGS not being liquid this is a big deal.

And I beg you to add this to the code it is relatively easy to do. And should have been the default way to import keys in the toolkit.

Going forward this is a must for BTS DACs

[carpet ride]

It's a failed startup.  Just like the real world, beware what you invest in


Sent from my iPhone using Tapatalk

[Riverhead]

It would be tough because a likely code hack like that would be in the binaries and not checked into GitHub (reason md5 is so important).

Also I can't comment on how ags is stored but since claiming requires a private key i3 doesn't have I doubt anything can be done. Only future snapshots would benefit and since ags snapshot is long in the books....

[Gentso1]

Guys, "tool" just means whenever someone releases a DAC to check for signed message instead of asking for private key when importing. That's it! Possibly even a one line change in the code. I am really shocked DNS didn't implement that. Should be extremely easy to do.

Interesting. Wonder if cob will do this. If not we can ask for it in the wallet [ANN] thread. In the meantime may be best for pts holders to transfer holdings to a new address before Oct 10th. That will prevent any past leaks from claiming your Notes.

Nothing can be done about ags holders though correct?

None of the devs have built such a tool yet because we trust ourselves. It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

Can you comment if it would be possible for LTS or any DAC to use ags private keys to claim future distributions?
How hard would it be for a dev to take a look at LTS code to confirm or deny the above flaw, not fix just confirm to see if it was intentional or truly bad timing?

[Riverhead]

It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

Seems like a good use of dev funds for a 3rd party DAC to strip down and have audited such an import mechanism. Their DAC would then be more appealing to the PTS/AGS crowd.

[callmeluc]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

Why give it up so easy? Did you realize that it's a destruction to the reputation of I3 and yourself? Because of the connection between you, PTS, I3 and this community, and your "generosity" to AGS/PTS, lots of people thought it's a I3 product.

Or maybe we can just call it mmc 3.0

[toast]

None of the devs have built such a tool yet because we trust ourselves. It is simple to implement in the toolkit right now but then you either have to strip it down until it's small enough to audit (the hard part) or you'd just be trusting us anyway.

[Riverhead]

DNS is falling because there's no product yet :-). Toast is trusted and is using the Bitshares toolkit. Signed blocks vs import private key is still doable before a product is released.

[mf-tzo]

Interesting...so that might be the reason why DNS keeps falling...Some people have realized that and sell them maybe?

I think we should discuss this in the relevant thread...

[Riverhead]

Guys, "tool" just means whenever someone releases a DAC to check for signed message instead of asking for private key when importing. That's it! Possibly even a one line change in the code. I am really shocked DNS didn't implement that. Should be extremely easy to do.

Interesting. Wonder if cob will do this. If not we can ask for it in the wallet [ANN] thread. In the meantime may be best for pts holders to transfer holdings to a new address before Oct 10th. That will prevent any past leaks from claiming your Notes.

[bitmeat]

Guys, "tool" just means whenever someone releases a DAC to check for signed message instead of asking for private key when importing. That's it! Possibly even a one line change in the code. I am really shocked DNS didn't implement that. Should be extremely easy to do.

[Gentso1]

I have read that too.

I hope until then nothing really bad happens and everything crashes because then I will have spent 1 year of my life for nothing and be left keeping the bag as usual...

I have also read it and it was briefly mentioned when lts was launched. However when keyid was launched to claim ags we had to import private keys again. 

[mf-tzo]

I have read that too.

I hope until then nothing really bad happens and everything crashes because then I will have spent 1 year of my life for nothing and be left keeping the bag as usual...

[Riverhead]

I have read I3 is working on a tool to safely claim shares in new dacs

[mf-tzo]

Suddenly I feel very reassured that I haven't used my AGS to claim any LTS...

We need something to securely claim shares from AGS at some point.

I haven't even claimed BTSX,DNS from AGS yet since I don't feel comfortable with the current clients, plus I am here for the looooonnnnggggg run even if I am missing a lot of trading opportunities...

[jsidhu]

When freetrade signed on to do this project many on bitcointalk brought up his history with memory coin I believe it was. I went through the thread some time ago and I remeber thinking to myself it seemed a little shady but not nearly enough evidence to stand on its on. How ever when you put that and now this into play we have a dev who just at best case circumstances was "at the wrong place at the wrong time" so to speak.  My biggest concern now is:

1."30% will be targeted at the public addresses of individuals who can be helpful to LottoShares DAC (devs, exchanges, service providers, marketeers etc - email memorycoincc@gmail.com to make a pitch, full list to be provided at launch)" https://bitsharestalk.org/index.php?topic=4691.0 
"10% will be proportionally distributed to MemoryCoin (MMC) holders (Block #39,983)" a project he worked as a dev before, please read the thread and notice their mature date is the first on the list and much before ags/pts would have had access to their funds.
2. private keys were used to claim lts holdings and it is not far fetched to think that freetrade my now have anyone's private keys who claimed ags/pts. pts not being much of a problem becasue funds can be moved but ags.......
3.Future projects he is working on. While the above is circumstantial when you put it all together it looks, not favorable.

I for one do not want to see the above dev working on any I3 projects until the nature of this flaw is explored by someone who understands code and a little explaining is done on the devs part as to how much lts he claimed and sold before "announcing" a fatal blow to lts.

*Please note I have not used the words fraud or scammer I am merely saying hey lets take a closer look at this because its odd and if indeed he is up to something we should obviously not have him working on future projects. This also highlights the immediate need to have a system other then submitting of private keys.

[Gentso1]

his forum also seems to be down with out even a message http://forum.lottoshares.org/topic/4/lottoshares-you-probably-wouldn-t-be-interested-in-this-launch-july-8th

[Gentso1]

When freetrade signed on to do this project many on bitcointalk brought up his history with memory coin I believe it was. I went through the thread some time ago and I remeber thinking to myself it seemed a little shady but not nearly enough evidence to stand on its on. How ever when you put that and now this into play we have a dev who just at best case circumstances was "at the wrong place at the wrong time" so to speak.  My biggest concern now is:

1."30% will be targeted at the public addresses of individuals who can be helpful to LottoShares DAC (devs, exchanges, service providers, marketeers etc - email memorycoincc@gmail.com to make a pitch, full list to be provided at launch)" https://bitsharestalk.org/index.php?topic=4691.0 
"10% will be proportionally distributed to MemoryCoin (MMC) holders (Block #39,983)" a project he worked as a dev before, please read the thread and notice their mature date is the first on the list and much before ags/pts would have had access to their funds.
2. private keys were used to claim lts holdings and it is not far fetched to think that freetrade my now have anyone's private keys who claimed ags/pts. pts not being much of a problem becasue funds can be moved but ags.......
3.Future projects he is working on. While the above is circumstantial when you put it all together it looks, not favorable.

I for one do not want to see the above dev working on any I3 projects until the nature of this flaw is explored by someone who understands code and a little explaining is done on the devs part as to how much lts he claimed and sold before "announcing" a fatal blow to lts.

*Please note I have not used the words fraud or scammer I am merely saying hey lets take a closer look at this because its odd and if indeed he is up to something we should obviously not have him working on future projects. This also highlights the immediate need to have a system other then submitting of private keys.

[jsidhu]

I dont believe he's a scammer either but I do believe his rep is damaged enough for people to stop buying into his ideas from this point on. He decided the problems were too hard and give up instead of asking for help if he did I am not aware of that... he moved on to other things and gave up on his communitie(s)... so what makes you think the same thing wouldn't happen with his next project? I don't think he should be given any benefit of any doubt for new projects like he has been given before... I doubt he will do anything new in this space now anyway.

[Riverhead]

or it'll get snapshotted into Just Dice Style DAC.

I'd really recommend not snapshotting LTS for anything. Care to guess who's the biggest holder of LTS? Do you want to reward him for this?

An excellent point.

I do not believe Free Trade is a scammer and had this all planed out from the start. I think he is someone that genuinely wants to finish the projects he starts but his real life makes this impossible (from the little bits I've been able to gather, I do not know him personally).

While the intent was never malicious it should be taken under consideration that if/when he starts another project there is a very high likelihood of it being abandoned and the market needs to price the risk accordingly.

[GaltReport]

or it'll get snapshotted into Just Dice Style DAC.

I'd really recommend not snapshotting LTS for anything. Care to guess who's the biggest holder of LTS? Do you want to reward him for this?

ah, good point!

[pc]

or it'll get snapshotted into Just Dice Style DAC.

I'd really recommend not snapshotting LTS for anything. Care to guess who's the biggest holder of LTS? Do you want to reward him for this?

[GaltReport]

Kinda thought this would happen when I discovered that the LTS I was "given" couldn't be used....ah, one born every minute I guess.

[Riverhead]

First MMC now LTS... I doubt anyone will learn to trust this dev again.

Hopefully either someone will pick up the project or it'll get snapshotted into Just Dice Style DAC.

[jsidhu]

First MMC now LTS... I doubt anyone will learn to trust this dev again.

[CossCrypto]

Given this news why is LTS up 20%? Granted, it's 20% of a very small number but someone is buying up LTS.

This is just because the trading volume is inexistent and the spread inbetween buy and sell orders is about 20%. So if I now sell 1 LTS on Bter it goes down 20% again. I dumped anyway a few hours back after reading Freetrade's answer to this.


edit: total buy orders left are about 60$...maybe one guy just forgot about his buy order. After that 60$, LTS is dead.

[Riverhead]

Given this news why is LTS up 20%? Granted, it's 20% of a very small number but someone is buying up LTS.

https://bter.com/trade/lts_btc

[liondani]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

So why don't you think about the possibility to create a dpos lotto coin using the bitshares-toolkit and make a snapshot on LTS (POW) so you can fairly distribute the dpos lottocoins to the current LTS holders ?
Why do you punish everybody that trusted you leaving the project?
Many have invested in this and they loose their investment because... you leave?

[Riverhead]

Seems this type of DAC has new life in the Just Dice (JDS) project. From what I can see in github it's gone through 17 dry runs.

https://bitsharestalk.org/index.php?topic=9393.msg121814#msg121814

[liondani]

It seems like it is the first official DAC scam... (Sorry to say that but it really smell like that! Hope I am totally wrong, but the first signs where already there before lunch... )
Hope nobody made the mistake to share his AGS/PTS keys !!!

That's why we are screaming we need a tool for that exact reason !!!
We don't want expose our AGS/PTS keys to untrusted individuals in future.



PS so for everybody has used his key for this project it's better to claim his AGS/PTS on new DACs immediately  after lunch and of course NOT for third party DACS before a tool is out there securing us !!!

Are you saying that he could have recorded all private key inputs of LTS users with the wallet??

Is it not possible? Can a trusted programmer/developer that has reviewed the code ensure us that this is not the case?
I just want to make you all think about the possibility's that this can/could happen at some time especially from third party DA Cs and push our DEVs  NOW to give us a tool that eliminate our concerns !

Logically speaking I think it could be possible for sure to use a wallet as a kind of "keylogger"...that sucks. Now I'll have to be worried of somebody else holding my private keys only because I liked his DAC...

I hope nobody will be worried in the future because we can claim our AGS/PTS without the need to expose our private keys (waiting our devs to solve that)
And it would be great if someone that is trusted can ensure as that the LTS-wallet code was/is ok.

[CossCrypto]

It seems like it is the first official DAC scam... (Sorry to say that but it really smell like that! Hope I am totally wrong, but the first signs where already there before lunch... )
Hope nobody made the mistake to share his AGS/PTS keys !!!

That's why we are screaming we need a tool for that exact reason !!!
We don't want expose our AGS/PTS keys to untrusted individuals in future.



PS so for everybody has used his key for this project it's better to claim his AGS/PTS on new DACs immediately  after lunch and of course NOT for third party DACS before a tool is out there securing us !!!

Are you saying that he could have recorded all private key inputs of LTS users with the wallet??

Is it not possible? Can a trusted programmer/developer that has reviewed the code ensure us that this is not the case?
I just want to make you all think about the possibility's that this can/could happen at some time especially from third party DA Cs and push our DEVs  NOW to give us a tool that eliminate our concerns !

Logically speaking I think it could be possible for sure to use a wallet as a kind of "keylogger"...that sucks. Now I'll have to be worried of somebody else holding my private keys only because I liked his DAC...

[liondani]

It seems like it is the first official DAC scam... (Sorry to say that but it really smell like that! Hope I am totally wrong, but the first signs where already there before lunch... )
Hope nobody made the mistake to share his AGS/PTS keys !!!

That's why we are screaming we need a tool for that exact reason !!!
We don't want expose our AGS/PTS keys to untrusted individuals in future.



PS so for everybody has used his key for this project it's better to claim his AGS/PTS on new DACs immediately  after lunch and of course NOT for third party DACS before a tool is out there securing us !!!

Are you saying that he could have recorded all private key inputs of LTS users with the wallet??

Is it not possible? Can a trusted programmer/developer that has reviewed(or will) the code ensure us that this is not the case?
I just want to make you all think about the possibility's that this can/could happen at some time especially from third party DA Cs and push our DEVs  NOW to give us a tool that eliminate our concerns !

[CossCrypto]

It seems like it is the first official DAC scam... (Sorry to say that but it really smell like that! Hope I am totally wrong, but the first signs where already there before lunch... )
Hope nobody made the mistake to share his AGS/PTS keys !!!

That's why we are screaming we need a tool for that exact reason !!!
We don't want expose our AGS/PTS keys to untrusted individuals in future.



PS so for everybody has used his key for this project it's better to claim his AGS/PTS on new DACs immediately  after lunch and of course NOT for third party DACS before a tool is out there securing us !!!

Are you saying that he could have recorded all private key inputs of LTS users with the wallet??

[liondani]

It seems like it is the first official DAC scam... (Sorry to say that but it really smell like that! Hope I am totally wrong, but the first signs where already there before lunch... )
Hope nobody made the mistake to share his AGS/PTS keys !!!

That's why we are screaming we need a tool for that exact reason !!!
We don't want expose our AGS/PTS keys to untrusted individuals in future.



PS so for everybody has used his key for this project it's better to claim his AGS/PTS on new DACs immediately  after lunch and of course NOT for third party DACS before a tool is out there securing us !!!

[Gentso1]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

Any more insight into this?  Is there another dev working on LTS?  Will you be porting LTS over to a BTSX model?  This just seems very blunt.

I am curious if the dev fund of lts was left alone or liquidated before this announcement, also the time seems odd as its right before ags/pts share's mature...

Care to comment on how much of the dev fund was cashed out before your announcement freetrade?

[Brekyrself]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

Any more insight into this?  Is there another dev working on LTS?  Will you be porting LTS over to a BTSX model?  This just seems very blunt.

[biophil]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

So this is the official LTS death-rattle?

Sent from my SCH-S720C using Tapatalk 2

[BTSdac]

LTS of most of PTSer and AGSer are locked now , -5%,-5%

[FreeTrade]

Update:

I've been trying to resolve two problems with LottoShares but have not managed to do so.

The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.

The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.

Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.

Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.

[CossCrypto]

bitcointalk user emrebey said the following on 20/09/2014;

regarding the dev inactivity,

just have a little patience. freeTrade dealing with some real life stuff, he will come back soon.

Thanks for the heads up, hope he'll manage to solve his issues soon

[Ben Mason]

https://bitcointalk.org/index.php?topic=694341.600

bitcointalk user emrebey said the following on 20/09/2014;

regarding the dev inactivity,

just have a little patience. freeTrade dealing with some real life stuff, he will come back soon.

[pc]

I can't image he'd "just abandon" it. It had a good start, and he can't have dumped many of his coins in such a short time. He would've been much better off by continuing to support it.

[jwiz168]

Just like the original memorycoin, he just abandoned the project. Sad to say he is identified within Bitshares community.

[pc]

FreeTrade has been missing for almost 4 weeks now. Hasn't logged in since Sep 8 neither here nor on btt. Block explorer at 42tx is stuck, lottoshares.org forum has been down for about 2 weeks.
I wonder if he's been run over by a bus or something. Maybe the bus was driven by an FBI agent... :-/

[CossCrypto]

LTS is not working properly since weeks now.
Price on exchanges is falling to the ground. And wallet is no fun. Did the dev give up on this project? It was a nice one

[pgbit]

Are things working as expected now with LTS?

[Ben Mason]

Hey Freetrade, do you know why the games have stopped producing results?  I have a couple of games that appear to be in limbo.  Dice Game: Roll Odd Number | Block:70056  | . . .  and Played: 2 13 24 25 31 35 | Block:70207  | . . .

I'm running 1.0.7, reinstalled and rescanned....I think some others have had the same issue to.  All the best.