Subscribe to Snapshot Labs
>470K subscribers
Snapshot LabsIntroducing Snapshot v2: A new interface for enhanced DAO governance
Snapshot Labs is excited to announce the beta release of Snapshot v2, a new interface to start the evolutionary journey of a product that the web3 space has gotten to know so well.Governance is more than voting. As the most used tool in DAO governance, Snapshot is expanding in order to provide more of what DAO communities need, in one place. The vision for Snapshot v2 is to unite the governance flow on one platform. We want to reduce the friction that DAO participants often have to endure whe...
Snapshot LabsIntroducing Snapshot's onchain voting protocol: Snapshot X
Snapshot Labs is pleased to announce the launch of Snapshot X, our new fully onchain voting protocol integrated seamlessly into the recently launched Snapshot v2 interface. Snapshot X combines the best of both worlds: the security and verifiability of onchain voting and trustless execution, plus the frictionless ease and modularity that Snapshot is known for. With Snapshot X, DAO communities can continue to enjoy the best governance user experience while adding on the security guarantees that...
Snapshot LabsStarknet governance launches on Snapshot X
Following yesterday’s launch of Snapshot X, we’re excited to announce that Starknet has deployed its governance onto the Snapshot X protocol, via the Starknet Governance Hub, a custom UI designed by Yuki Labs. Starknet’s first onchain vote via Snapshot X is live now until September 13, 2024, to decide on a potential STRK staking program. If you’re a STRK holder, be sure to cast your vote on this pivotal decision. We look forward to onboarding more great projects onto Snapshot X soon! Create y...
Snapshot LabsIntroducing Snapshot v2: A new interface for enhanced DAO governance
Snapshot Labs is excited to announce the beta release of Snapshot v2, a new interface to start the evolutionary journey of a product that the web3 space has gotten to know so well.Governance is more than voting. As the most used tool in DAO governance, Snapshot is expanding in order to provide more of what DAO communities need, in one place. The vision for Snapshot v2 is to unite the governance flow on one platform. We want to reduce the friction that DAO participants often have to endure whe...
Snapshot LabsIntroducing Snapshot's onchain voting protocol: Snapshot X
Snapshot Labs is pleased to announce the launch of Snapshot X, our new fully onchain voting protocol integrated seamlessly into the recently launched Snapshot v2 interface. Snapshot X combines the best of both worlds: the security and verifiability of onchain voting and trustless execution, plus the frictionless ease and modularity that Snapshot is known for. With Snapshot X, DAO communities can continue to enjoy the best governance user experience while adding on the security guarantees that...
Snapshot LabsStarknet governance launches on Snapshot X
Following yesterday’s launch of Snapshot X, we’re excited to announce that Starknet has deployed its governance onto the Snapshot X protocol, via the Starknet Governance Hub, a custom UI designed by Yuki Labs. Starknet’s first onchain vote via Snapshot X is live now until September 13, 2024, to decide on a potential STRK staking program. If you’re a STRK holder, be sure to cast your vote on this pivotal decision. We look forward to onboarding more great projects onto Snapshot X soon! Create y...
Share Dialog
Share Dialog
Our Hub API has always been open for anyone to query as we wanted to provide equal access to information for our users and integrators. This however has led to several issues related to API performance. To give you a better idea - we are receiving over 540 million requests per month.
While well-structured and timed requests are not posing a threat to the stability of the service we have seen some incidents caused by sudden outbursts of incoming requests, caused either by bots spamming the API or poor-quality code falling into endless loops.
We want to make sure that we limit the risk of API downtime and provide a reliable and continuous service. Therefore we decided to implement API Keys to make sure that the requests are coming from genuine users.
Do not worry if you are a current API user!
The API will be still available in the current form until September 12th to enable a smooth transition for everyone. After September 12th you will be able to query it without a key but at a much lower limit.
If you haven’t already please fill in the following form:
We will review your submission and whitelist the address you provided in the form.
After 72 hours from the form submission you can continue with the next steps:
Go to https://app.mycrypto.com/sign-message and connect your wallet using the account you provided in the submission form above.
Sign the message with the keyword generateKey.
Copy the signature and run the below curl command. Make sure to use the signature hash from step 5 in the sig param, do not paste the entire response after signing the message.
curl --location 'https://keycard.snapshot.org' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
"jsonrpc": "2.0",
"method": "generate_key",
"params": {
"sig": "<SIGNATURE_HASH>"
},
"id": "123456789"
}'
Example:
...
"method": "generate_key",
"params": {
"sig": "0x85bcabdeb3b43131364d21b32f8c74124d155009fc9d6d40901b4b725f23e0ac632808ebb00f3569bf875ded07b61ac5163ebe757b0897278ab276cdc982e3001c"
},
...
That’s it, you should receive your unique API Key in the response!
During the next three months, the limits for keyless access to the API will not change:
🔓 No API Key: 120 requests every 20 seconds.
🔑 With the API Key: 2 million requests per month.
After September 12th, the limits will be updated to:
🔓 No API Key: 100 requests every minute.
🔑 With the API Key: 2 million requests per month.
If you are getting close to 2M requests a month please reach out to our team directly on Discord by creating a new ticket in the #helpdesk-tickets channel.
The only change you need to make is to add the apiKey in the headers of your request:
curl 'https://hub.snapshot.org/graphql?' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR-API-KEY>' \
--data-raw '{"query":"\n{\n space(id:\"snapshot.dcl.eth\"){\n id\n name\n members\n}\n}","variables":null}' \
--compressed
To obtain higher rate limits on the Hub API use, apply for an API Key.
Contribute to snapshot-labs/keycard development by creating an account on GitHub.
Our Hub API has always been open for anyone to query as we wanted to provide equal access to information for our users and integrators. This however has led to several issues related to API performance. To give you a better idea - we are receiving over 540 million requests per month.
While well-structured and timed requests are not posing a threat to the stability of the service we have seen some incidents caused by sudden outbursts of incoming requests, caused either by bots spamming the API or poor-quality code falling into endless loops.
We want to make sure that we limit the risk of API downtime and provide a reliable and continuous service. Therefore we decided to implement API Keys to make sure that the requests are coming from genuine users.
Do not worry if you are a current API user!
The API will be still available in the current form until September 12th to enable a smooth transition for everyone. After September 12th you will be able to query it without a key but at a much lower limit.
If you haven’t already please fill in the following form:
We will review your submission and whitelist the address you provided in the form.
After 72 hours from the form submission you can continue with the next steps:
Go to https://app.mycrypto.com/sign-message and connect your wallet using the account you provided in the submission form above.
Sign the message with the keyword generateKey.
Copy the signature and run the below curl command. Make sure to use the signature hash from step 5 in the sig param, do not paste the entire response after signing the message.
curl --location 'https://keycard.snapshot.org' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
"jsonrpc": "2.0",
"method": "generate_key",
"params": {
"sig": "<SIGNATURE_HASH>"
},
"id": "123456789"
}'
Example:
...
"method": "generate_key",
"params": {
"sig": "0x85bcabdeb3b43131364d21b32f8c74124d155009fc9d6d40901b4b725f23e0ac632808ebb00f3569bf875ded07b61ac5163ebe757b0897278ab276cdc982e3001c"
},
...
That’s it, you should receive your unique API Key in the response!
During the next three months, the limits for keyless access to the API will not change:
🔓 No API Key: 120 requests every 20 seconds.
🔑 With the API Key: 2 million requests per month.
After September 12th, the limits will be updated to:
🔓 No API Key: 100 requests every minute.
🔑 With the API Key: 2 million requests per month.
If you are getting close to 2M requests a month please reach out to our team directly on Discord by creating a new ticket in the #helpdesk-tickets channel.
The only change you need to make is to add the apiKey in the headers of your request:
curl 'https://hub.snapshot.org/graphql?' \
-H 'content-type: application/json' \
-H 'x-api-key: <YOUR-API-KEY>' \
--data-raw '{"query":"\n{\n space(id:\"snapshot.dcl.eth\"){\n id\n name\n members\n}\n}","variables":null}' \
--compressed
To obtain higher rate limits on the Hub API use, apply for an API Key.
Contribute to snapshot-labs/keycard development by creating an account on GitHub.
No comments yet