Error 500 when using endpoint from Orbs

Answered

Hi everyone

I use API v4. In the docs there is example of getting block by unix time: https://mainnet-v4.tonhubapi.com/block/utime/1680031682. Here everything is clear. But if I try to use endpoint from @orbs-network/ton-access request https://ton.access.orbs.network/44A1c0ff5Bd3F8B62C092Ab4D238bEE463E644A1/1/mainnet/ton-api-v4/block/utime/1680031682 returns 500 error.

Are there any restrictions when use endpoints from Orbs?

  				
Posted 
	10 months ago

								Edited 
	10 months ago

					More
				  		
  Report
		
					Sergei Krivochenko
				
					36
					 × 3

Revisions

Votes Newest

Answers

Hi,

This error caused by trying to access an old block from a node which does not store this information for long period.

All nodes in the network have some default retention for historical data and fetching old blocks requires accessing archive nodes which stores this information for longer periods.

We are currently working to dramatically increase the retention for archive nodes and soon you will be able to access old blocks.

 						
				1

				1
Posted 
	10 months ago

								Edited 
	10 months ago

					More
				  		
  Report
		
					Ami Hazbany
				
					60
					 × 2

Thanks for your answer

— Sergei Krivochenko 10 months ago

If I run my own instance with docker

docker run -e TON_CONFIG=https://ton.org/global-config.json -p 3000:3000 tonwhales/ton-api-v4:v41

, will it be possible to get old blocks?

— Sergei Krivochenko 10 months ago

I ask because currently I can't run it because of issue https://github.com/ton-community/ton-api-v4/issues/9

— Sergei Krivochenko 10 months ago

Most of the nodes in the global config will not provide long history as the default when installing new node is 1 week for block state.

— Ami Hazbany 10 months ago

Revisions

Write your answer

15K Views

1 Answer

10 months ago