EIP 665 - Add precompile for Ed25519

[oberstet]

See also this PR requesting the same #665

The PR here is more complete and takes up the feedback of @pirapira

[Arachnid]

Existing precompiles do not use function selectors (for example, the RSA precompile). I think it'd be a good idea to remain consistent with that, and specify this in terms of call data.

[oberstet]

Not sure what you mean, could you expand? Note that m is supposed to be the message to be signed, and is needed by the actual function body.

[Arachnid]

Take a look at http://eips.ethereum.org/EIPS/eip-196 for instance - the precompile takes call data that is the direct encoding of the parameters, with no function selector (eg, it's not a Solidity-standard multi-function contract). All precompiles so far are like this; it'd be a good idea to retain consistency here.

[oberstet]

Ok, got it. Thanks for pointing me in the right direction! So I believe the changes I pushed should address that.

[Arachnid]

This is a courtesy notice to let you know that the format for EIPs has been modified slightly. If you want your draft merged, you will need to make some small changes to how your EIP is formatted:

• Frontmatter is now contained between lines with only a triple dash ('---')
• Headers in the frontmatter are now lowercase.

If your PR is editing an existing EIP rather than creating a new one, this has already been done for you, and you need only rebase your PR.

In addition, a continuous build has been setup, which will check your PR against the rules for EIP formatting automatically once you update your PR. This build ensures all required headers are present, as well as performing a number of other checks.

Please rebase your PR against the latest master, and edit your PR to use the above format for frontmatter. For convenience, here's a sample header you can copy and adapt:

---
eip: <num>
title: <title>
author: <author>
type: [Standards Track|Informational|Meta]
category: [Core|Networking|Interface|ERC] (for type: Standards Track only)
status: Draft
created: <date>
---

[oberstet]

@gcolvin Awesome, thx for merging!

As I am new here, may I ask for a tip? What is the best / acceptable way to promote or support this EIP?

• Should I come up with an implementation PR for say go-ethereum?
• Should I go to Ethereum forums/IRC and nudge people to support this EIP, "organizing support"?
• Anything else? Did I miss some docs?

Thanks again!

[Arachnid]

A good first step would be to ask @Souptacular to add this to the agenda for the next All Core Devs, and join the meeting to describe your EIP.

Being able to show a POC implementation on one or more clients wouldn't hurt.

[oberstet]

@Arachnid thanks again for your hints! Will follow your advice.