Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: replace old Rinkeby reference #1940

Merged
merged 1 commit into from
Jan 30, 2024
+6 −1
Merged

docs: replace old Rinkeby reference #1940

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/many-flies-count.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@api3/airnode-protocol': patch
---

Replace old Rinkeby reference
2 changes: 1 addition & 1 deletion packages/airnode-protocol/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ The protocols are extended in functionality through _authorizers_. An authorizer
called statically to check if a particular request should be responded to, e.g., if its requester is whitelisted. While
deploying an Airnode, the operator specifies the addresses of the authorizer contracts they want to use. (These
contracts may live on a chain different than the protocol contract, e.g., an Airnode can be configured to refer to a
mainnet authorizer for requests received from Rinkeby.) Then, whenever an Airnode receives a request, it will make a
mainnet authorizer for requests received from Sepolia.) Then, whenever an Airnode receives a request, it will make a
static call to its authorizers to determine if it should respond to the request.

The contracts that use the Airnode protocol to make API calls are called _requesters_. A requester can be a user-facing
Expand Down
Loading