You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[getNFTsForOwner](/reference/getnftsforowner-v3)| Retrieve the NFTs owned by a wallet address |
19
-
|[getOwnersForNFT](/reference/getownersfornft-v3)| Retrieve the owners of a given token |
20
-
|[getOwnersForContract](/reference/getownersforcontract-v3)| Retrieve all the owners for a given NFT contract, including snapshotting owners at any block number. |
21
-
|[isHolderOfContract](/reference/isholderofcontract-v3)| Check whether a given wallet owns any NFT in a collection |
22
-
|[getContractsForOwner](/reference/getcontractsforowner-v3)| Retrieve the list of NFT contracts from which a wallet address owns one or more tokens. |
23
-
|[getCollectionsForOwner](/reference/getcollectionsforowner-v3)| Gets all NFT collections held by an owner address. |
18
+
|[getNFTsForOwner](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-nf-ts-for-owner-v-3)| Retrieve the NFTs owned by a wallet address |
19
+
|[getOwnersForNFT](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-owners-for-nft-v-3)| Retrieve the owners of a given token |
20
+
|[getOwnersForContract](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-owners-for-contract-v-3)| Retrieve all the owners for a given NFT contract, including snapshotting owners at any block number. |
21
+
|[isHolderOfContract](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/is-holder-of-contract-v-3)| Check whether a given wallet owns any NFT in a collection |
22
+
|[getContractsForOwner](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-contracts-for-owner-v-3)| Retrieve the list of NFT contracts from which a wallet address owns one or more tokens. |
23
+
|[getCollectionsForOwner](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-collections-for-owner-v-3)| Gets all NFT collections held by an owner address. |
24
24
|[NFT Activity Webhook](/reference/nft-activity-webhook)| Receiving real-time updates for NFT Transfers and NFT mints |
|[getNFTsForContract](/reference/getnftsforcontract-v3)| Retrieve all the NFTs for a given contract or collection |
31
-
|[getNFTMetadata](/reference/getnftmetadata-v3)| Retrieve the metadata associated with a given NFT i.e. a specific tokenId |
32
-
|[getNFTMetadataBatch](/reference/getnftmetadatabatch-v3)| Retrieve the metadata associated with several NFTs across collections in a single request |
33
-
|[getContractMetadata](/reference/getcontractmetadata-v3)| Retrieve the metadata associated with a given contract or collection |
34
-
|[getContractMetadataBatch](/reference/getcontractmetadatabatch-v3)| Retrieve contract metadata for several different contracts in a single request |
35
-
|[computeRarity](/reference/computerarity-v3)| Compute the rarity of each attribute of an NFT. |
36
-
|[invalidateContract](/reference/invalidatecontract-v3)| Triggers metadata refresh for an NFT collection/refreshes stale metadata after a reveal |
37
-
|[refreshNftMetadata](/reference/refreshnftmetadata-v3)| Submit a request that Alchemy refresh the cached NFT metadata for a particular token. |
38
-
|[summarizeNFTAttributes](/reference/summarizenftattributes-v3)| Generate a summary of attribute prevalence for an NFT collection. |
39
-
|[searchContractMetadata](/reference/searchcontractmetadata)| Search the metadata across contracts for specific keywords |
30
+
|[getNFTsForContract](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/get-nf-ts-for-contract-v-3)| Retrieve all the NFTs for a given contract or collection |
31
+
|[getNFTMetadata](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/get-nft-metadata-v-3)| Retrieve the metadata associated with a given NFT i.e. a specific tokenId |
32
+
|[getNFTMetadataBatch](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/get-nft-metadata-batch-v-3)| Retrieve the metadata associated with several NFTs across collections in a single request |
33
+
|[getContractMetadata](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/get-contract-metadata-v-3)| Retrieve the metadata associated with a given contract or collection |
34
+
|[getContractMetadataBatch](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/get-contract-metadata-batch-v-3)| Retrieve contract metadata for several different contracts in a single request |
35
+
|[computeRarity](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/compute-rarity-v-3)| Compute the rarity of each attribute of an NFT. |
36
+
|[invalidateContract](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/invalidate-contract-v-3)| Triggers metadata refresh for an NFT collection/refreshes stale metadata after a reveal |
37
+
|[refreshNftMetadata](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/refresh-nft-metadata-v-3)| Submit a request that Alchemy refresh the cached NFT metadata for a particular token. |
38
+
|[summarizeNFTAttributes](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/summarize-nft-attributes-v-3)| Generate a summary of attribute prevalence for an NFT collection. |
39
+
|[searchContractMetadata](/reference/nft-api-endpoints/nft-api-endpoints/nft-metadata-endpoints/search-contract-metadata-v-3)| Search the metadata across contracts for specific keywords |
|[getSpamContracts](/reference/getspamcontracts-v3)| Retrieve a list of contracts marked as spam |
46
-
|[isSpamContract](/reference/isspamcontract-v3)| Returns whether a specific contract is marked as spam or not |
47
-
|[isAirdropNFT](/reference/isairdropnft-v3)| Returns whether a token is marked as an airdrop or not |
48
-
|[reportSpam](/reference/reportspam-v3)| Report a contract if you think its spam |
45
+
|[getSpamContracts](/reference/nft-api-endpoints/nft-api-endpoints/nft-spam-endpoints/get-spam-contracts-v-3)| Retrieve a list of contracts marked as spam |
46
+
|[isSpamContract](/reference/nft-api-endpoints/nft-api-endpoints/nft-spam-endpoints/is-spam-contract-v-3)| Returns whether a specific contract is marked as spam or not |
47
+
|[isAirdropNFT](/reference/nft-api-endpoints/nft-api-endpoints/nft-spam-endpoints/is-airdrop-nft-v-3)| Returns whether a token is marked as an airdrop or not |
48
+
|[reportSpam](/reference/nft-api-endpoints/nft-api-endpoints/nft-spam-endpoints/report-spam-v-3)| Report a contract if you think its spam |
|[getFloorPrice](/reference/getfloorprice-v3)| Retrieve the floor price of a NFT collection by marketplace |
55
-
|[getNFTSales](/reference/getnftsales-v3)| Retrieve NFT sales data across marketplaces |
54
+
|[getFloorPrice](/reference/nft-api-endpoints/nft-api-endpoints/nft-sales-endpoints/get-floor-price-v-3)| Retrieve the floor price of a NFT collection by marketplace |
55
+
|[getNFTSales](/reference/nft-api-endpoints/nft-api-endpoints/nft-sales-endpoints/get-nft-sales-v-3)| Retrieve NFT sales data across marketplaces |
Copy file name to clipboardExpand all lines: fern/api-reference/data/nft-api/nft-ownership-endpoints/getnftsforowner-v3.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: NFTs By Owner
3
3
description: getNFTsForOwner - Retrieves all NFTs currently owned by a specified address. This endpoint is supported on Ethereum and many L2s, including Polygon, Arbitrum, Optimism, Base, World Chain and more. See the full list of supported networks here .
4
4
subtitle: getNFTsForOwner - Retrieves all NFTs currently owned by a specified address. This endpoint is supported on Ethereum and many L2s, including Polygon, Arbitrum, Optimism, Base, World Chain and more. See the full list of supported networks here .
Copy file name to clipboardExpand all lines: fern/tutorials/getting-started/api-security-and-authentication/how-to-use-api-keys-in-http-headers.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ Please note that while we're using a basic Node.js project here for demonstratio
91
91
92
92
## Making the API Requests
93
93
94
-
With your API key at hand and the project set up, you can now start making HTTP header-based requests. To demonstrate the process, we'll use two major JavaScript libraries: Axios and Ethers.js. We'll make requests to the [`eth_getBalance`](/reference/eth-getbalance) method (JSON-RPC API) and [getNFTsForOwner](/reference/getnftsforowner-v3) NFT API method (Enhanced API) for showcasing.
94
+
With your API key at hand and the project set up, you can now start making HTTP header-based requests. To demonstrate the process, we'll use two major JavaScript libraries: Axios and Ethers.js. We'll make requests to the [`eth_getBalance`](/reference/eth-getbalance) method (JSON-RPC API) and [getNFTsForOwner](/reference/nft-api-endpoints/nft-api-endpoints/nft-ownership-endpoints/get-nf-ts-for-owner-v-3) NFT API method (Enhanced API) for showcasing.
An uncle block is **a block that did not get mined onto the canonical chain.** Only one block can be mined and acknowledged as canonical on the blockchain. The remaining blocks are uncle blocks. When two or more miners produce blocks at nearly the same time, uncle blocks are created.
10
+
Imagine Ethereum as a worldwide group chat where everyone is trying to add the next message (block) at the same time. Only one message can become the official next one. Sometimes two miners create a valid block at almost the same moment.
11
11
12
-
Uncle blocks are similar to orphan blocks on Bitcoin but have subtle distinctions connected with the Ethereum protocol. Uncle blocks are valid blocks that the network has rejected. Miners get paid for producing an uncle block, unlike an orphan block, where miners don't get rewarded.
12
+
Both blocks are valid.
13
+
Only one gets added to the official chain.
14
+
The other block becomes an uncle block.
13
15
14
-
***
16
+
## Why do uncle blocks happen?
15
17
16
-
## Why do uncle blocks occur?
18
+
Ethereum nodes are spread all over the world. When one miner finds a block, it takes a short time for that block to reach the rest of the network. During this short delay, another miner might also find a valid block.
17
19
18
-
Uncle blocks occur **when two or more miners create blocks at almost the same time.**
20
+
Now the network has two valid candidates for the next block.
21
+
Eventually the network settles on one.
22
+
The block that is not chosen becomes an uncle.
19
23
20
-
Uncle blocks occur because nodes on a network do not immediately accept a block into the blockchain. As a result, another miner can build and propagate their block at a similar time. To confirm the legitimacy of constructed blocks, they must be broadcast throughout the network to all nodes, which may cause latency concerns.
24
+
## ## Why are uncle blocks rewarded?
21
25
22
-
Ethereum introduces the uncle block technique to tackle the orphan block's security issues while improving transaction processing efficiency.
26
+
The miner who created the uncle block still performed real work and produced a valid block. It simply arrived a little too late. Ethereum gives a partial reward to encourage decentralization and to avoid punishing miners who are physically far from large mining pools.
23
27
24
-
***
28
+
## Do uncle blocks matter?
25
29
26
-
## How often do uncle blocks happen?
30
+
Yes. Even though they do not become part of the main chain, uncle blocks help the network in several ways:
27
31
28
-
Stale blocks are more common when nodes propagate blocks more slowly than substantial mining pools, resulting in a more significant prevalence of uncle blocks.
32
+
* They reduce wasted mining work
33
+
* They make mining more fair for smaller or slower miners
34
+
* They increase network security
35
+
* They give miners an incentive to include uncle references in future blocks
29
36
30
-
If the uncle rate rapidly increases and nodes leave the network, the gas limit may be too high, compromising network security.
37
+
## Summary
31
38
32
-
***
33
-
34
-
## What are uncle block rewards?
35
-
36
-
Uncle block rewards are rewards awarded to miners who create an uncle block included in a valid block added to the chain.
37
-
38
-
Uncle blocks are similar to stale blocks in bitcoin, except instead of being ignored, uncle blocks are awarded dependent on how new they are, with the most significant payout being 4.375 eth. An example of this reward can be found [here](https://etherscan.io/block/1378035).
39
-
40
-
***
41
-
42
-
## How do uncle block rewards get mined?
43
-
44
-
When miners of the main chain block reference uncle blocks, both the miner of the main chain block and the miner of the uncle block receive an additional reward.
45
-
46
-
Each block in the main chain can reference up to two uncle blocks, with each uncle receiving 1/32 of an entire block reward. The reward provided to the uncle block miner, on the other hand, declines over time.
47
-
48
-
***
49
-
50
-
## What is the difference between an uncle block and an orphan block?
51
-
52
-
The difference between an uncle block and an orphan block is that the Ethereum network rewards its uncle block miners. In contrast, the Bitcoin network does not compensate/reward orphan block miners.
39
+
An uncle block is a valid block that lost a timing race.
40
+
It was correct. It was just a little too slow to reach the network.##
0 commit comments