From 50ab79f9673c3bd5d6ef8ec6d0edc979bfdaa611 Mon Sep 17 00:00:00 2001 From: Derek Croote Date: Fri, 26 Jan 2024 22:48:05 -0800 Subject: [PATCH] docs: replace old Rinkeby reference --- .changeset/many-flies-count.md | 5 +++++ packages/airnode-protocol/README.md | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) create mode 100644 .changeset/many-flies-count.md diff --git a/.changeset/many-flies-count.md b/.changeset/many-flies-count.md new file mode 100644 index 0000000000..2abc82f19f --- /dev/null +++ b/.changeset/many-flies-count.md @@ -0,0 +1,5 @@ +--- +'@api3/airnode-protocol': patch +--- + +Replace old Rinkeby reference diff --git a/packages/airnode-protocol/README.md b/packages/airnode-protocol/README.md index 4f7507839c..cbd0e90450 100644 --- a/packages/airnode-protocol/README.md +++ b/packages/airnode-protocol/README.md @@ -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