API keys

[ligi]

follow up from this mail from infura:

7 days remaining to update your Infura API authentication | 7 days remaining to update your Infura API authentication | 7 days remaining to update your Infura API authentication
-- | -- | --
7 days remaining to update your Infura API authentication | 7 days remaining to update your Infura API authentication
7 days remaining to update your Infura API authentication
This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io. | This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io. | This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io.
This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io. | This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io.
This is the final message being sent prior to a very important change that will impact all users of the Infura API endpoints.  In this January 17th blog post,  we provided the latest timeline to deprecate our legacy API  authentication. Requests will start to require a Project ID generated  from the Infura Dashboard. More information on how to send requests  using a Project ID can be found in our docs. The next upcoming change will occur on:  March 27, 2019, 20:00 UTC Support will officially stop for all requests not sent using an Infura Dashboard-generated Project ID.  This transition will ensure that our service reliability and performance  is consistent for all users. For more information about the changes  please see the blog post linked above.  What do I need to do? If you haven’t done so already, create a free account at https://infura.io/register.  Once you log in to the Dashboard, simply create a new project, and your  Project ID (and associated Infura API endpoint URLs) will be generated.  Replace your old Infura URL in your code with the newly generated URL  from the Dashboard.  You may also create multiple projects to isolate traffic for multiple  dapps/use-cases. Stats can be viewed in aggregate or on a per-project  basis.  If you maintain a library that leverages Infura, please reach out directly to help you with this transition.  How do I know I am using the correct API endpoint URL? Prior to July 2018, your Infura API endpoint would have looked like this:  https://mainnet.infura.io/[YOUR_KEY]   The updated API endpoint using the new authentication generated in the Infura Dashboard will look like this:  https://mainnet.infura.io/v3/[PROJECT_ID]   If you have any questions please post them at community.infura.io or email us at support@infura.io.

wonder how we deal with mandatory api keys in rpc services

[pedrouid]

Yeah, I just noticed this too, we should follow the same pattern as you proposed for the faucets on issue #21

{
  ...
  faucets: ["https://goerli-faucet.slock.it/?address=%address%"]
}

but with the api key field instead

{
  ...
  rpc: ["https://mainnet.infura.io/v3/%api_key%"]
}

[ligi]

ack - the problem is just with the address it does not depend on the faucet - but with rpc it does - means we might have a infura_api_key and e.g. and etherscan_api_key

[pedrouid]

Let's just keep it simple and add the api_key parameter, anyone will be able to write simple logic to detect which key is required from the domain. I just updated my own API so I'm just going to push the PR for this issue since they're turning off the v1 API tomorrow night