Well it is not up to you to decide if we have all the information we need. That is up to your target audience.

But, let's go into a technical discussion, if that is what you want. I take this passage from your "whitepaper", which I would not really call a whitepaper, because it leaves out most of the details, and fails to connect the dots of information that are in it.

ad 1. What does the randomly generated private key look like? What are it's specifications?
ad 1. What does random mean in this case? What type/class of random generator are you using? Is it seeded, and if so: how?
ad 2. "A point on the curve is calculated into a 64 byte array". Many questions:
ad 2. What curve? what does a "point on the curve" mean? What point? what curve? What do you mean by "chosen" ? How does that work? Are there criteria to "choose" a point ?
ad 2. If you have 64 bytes, you have 64 bytes. An array is a representation of those bytes. What does that mean? How many elements are in your array? Is it associative or zero base indexed? How many bytes are used for the indices and how many bytes are for the data? The fact that the 64 bytes are an array implies that they are ordered. Why the ordering and how is the ordering preserved? Why the array representation? Sounds like bullshit to me.
ad 3. What do you mean by "collapsing a 64 byte array into a 16 byte array" ? Do you realise that if you reduce 64 bytes to 16 bytes, you are reducing entropy, thereby throwing away information? Lowering entropy is rarely a good idea in cryptographic systems. Please explain why this is a good idea in this case. Oh, and explain the "collapsing" algorithm.
ad 4. Why use 16 bytes for a constant? A constant is a constant. You are not using the 16 bytes entropy. Again: why is this a good idea? It does not add entropy nor information.
ad 4. What is the "Network Bytes" constant being used for? What is the purpose?
ad 5. Again lowering the entropy, by not using all bytes below '100' (assuming 100 in 10-base). Looks like you are throwing away all the advantages of high entropy in cryptographic systems, thereby making your system weaker with every step.

Please answer those questions, because they are a big big concern.

You're being childish. Why don't you just explain the beauty of your concept instead of getting all fiery wild about how I understood your statement about receiving REC. That's how I understood it. All you have to do is explain it so no one else will misinterpret it the way I did.

Private keys shouldn't just be given away casually. Asking for private keys raises red flags so thank heavens for people on the forum that can discern when something appears scammy.

There are people on this forum who - out of their good heart   - make it their purpose to expose scams/scammers, so while they do their investigation and point out some questionable portions of the announcement, it would be best to show proof that the one being accused isn't a fraud  

Private keys shouldn't just be given away casually. Asking for private keys raises red flags so thank heavens for people on the forum that can discern when something appears scammy.

There are people on this forum who - out of their good heart   - make it their purpose to expose scams/scammers, so while they do their investigation and point out some questionable portions of the announcement, it would be best to show proof that the one being accused isn't a fraud  

You have another thing coming bitalchemists or should I say Triswardhani, loljosh, mintodev, templar77, Carlos RT Ferguson, nite69, Thewolfofcrypto

You ain't fooling anyone

BE CAREFUL PEOPLE, THERE ARE A LOT OF RED FLAGS HERE:

• Anon dev
• No Escrow

Promises things that are to good to be true: it walks and talks like a duck.

• Github user is new and anon as well
• Source code on Github is just C# and lacks a LOT
• Source code on Github is C#, but OP mentions OSX and Linux as targets as well
• This is dead wrong:
  
  Quote
  Deposit any amount in BTC to 19vVPuzXPBUiNdnr6KZwYP9rAtdtWkDjqi until 2017/03/01
  Get x150 to your parallel REC address
  (using the same private key of the BTC address you've sent from; funds will be hardcoded into the genesis block).
  Launch is expected in September 2017.
  
  Private keys are private keys. They should never be available for anyone but you. The person who has your private keys, controls your Bitcoin. So if the dev states that he uses your private keys to create REC coins in a "parallel" address, that alone should be enough to abandon this coin/project.

Keep your private keys safe. Make sure nobody gets your private keys. If someone is after your private keys, he is after your bitcoin!

Any bounty available or to be announced? I would like to translate ann to spanish.

youre write
in launch coin and create coin is expected in September 2017.
but this now month january youre open ico selling, collect bitcoin investor and without escrow because coin still not ready

Its just not possible what you are trying to do.

To crack a private key with brute force will make millions of years even on Bitcoin ASICs.

This wont achieve anything except wasted electricity.

If you cant even explain what your doing and why your doing it and how it helps ect in more then a few sentences you don't deserve my time.

Good bye.

Still not following. Spell it out for me please.

Big changes are coming and Im prepared fro them. U will invest 300 million dollars in ecdsa attacks and will be rewarded with a small payment coming from a private key retrieved from btc address u control, but don't hope to see more payments coming in because the sending address will be vanished by greedy sharks and brave scavengers.

But how does that make money for you or anyone else unless you take the btc in the address.

Then what's the point. I don't get why you would want the first 8 bytes? What can you do with that?

Is there a mining method other than Amazon EC2 F1?

the LBC collider? ya the funds will be claimed, AFAIK, yes. We only work on the "puzzle transaction" there tho, not a free market or service, like this could be


ya its not decentralized nor a cryptocurrency, true.


my guess is they just want some financial comp for their idea and setting it up (what it seems like). Unfortunately most wont pay for an IDEA, but the service they might

ya haha its kinda hard to say WHAT they even need money for ;p

i am down for "Proof of Attack - Earn REC for only attempting to recover Bitcoin addresses"  -- but i still dont see why they will need funding to setup a server for people like at vanitypool where stuff can be posted for people to crack at. seems like that could be done out of pocket, maybe add a 1% fee to the "EDSCA Pool".
course on that note, we already have an open non profit at http://lbc.cryptoguru.org:5000/about that is as i understand it basically an "EDSCA Pool"  (tho not set up for incentives as this maybe could be)

idk, time will tell ;p

You want to do an ico to raise money to rob people of their btc, do I understand this correctly?