Hyperliquid API Announcements
Ir al canal en Telegram
Mostrar más
El país no está especificadoCriptomonedas67 755
440
Suscriptores
+1624 horas
+737 días
+20830 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
diciembre '24
diciembre '24
+272
en 0 canales
noviembre '24
+104
en 0 canales
Get PRO
octubre '24
+56
en 0 canales
Get PRO
septiembre '24
+211
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 21 diciembre | +15 | |||
| 20 diciembre | +11 | |||
| 19 diciembre | +13 | |||
| 18 diciembre | +14 | |||
| 17 diciembre | +27 | |||
| 16 diciembre | +17 | |||
| 15 diciembre | +19 | |||
| 14 diciembre | +7 | |||
| 13 diciembre | +8 | |||
| 12 diciembre | +10 | |||
| 11 diciembre | +16 | |||
| 10 diciembre | +31 | |||
| 09 diciembre | +6 | |||
| 08 diciembre | +1 | |||
| 07 diciembre | +5 | |||
| 06 diciembre | +2 | |||
| 05 diciembre | +12 | |||
| 04 diciembre | +12 | |||
| 03 diciembre | +6 | |||
| 02 diciembre | +7 | |||
| 01 diciembre | +33 |
Publicaciones del Canal
There will be a network upgrade around 8:30 UTC. Expect ~5 minutes of downtime.
| 2 | Based on user feedback, the tick formula will be updated on the next network upgrade to allow all integer prices regardless of number of sig figs. For example, after the change 123456 will be a valid price for BTC-USD. The change is already live on testnet. | 906 |
| 3 | There will be a network upgrade around 9:30 UTC. Expect ~5 minutes of downtime. | 1 057 |
| 4 | On the next network upgrade, the IP-based rate limiting logic will be updated to weight batched actions as 1 + floor(length / 40) instead of the previous constant weight of 1. For example, a batch sending 79 orders will have IP request weight of 2. This does not affect onchain user-based rate limits, info requests, or non-batched actions. | 1 193 |
| 5 | Some builder code improvements:
Builder codes are enabled for spot trading when fees are paid in USDC.
Builder codes are available for sub-accounts for both perps and spot trading.
Fills by builder address are now available at https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/{builder_address}/{YYYYMMDD}.csv.lz4
See docs for more details: https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes
Happy building | 1 214 |
| 6 | There will be a network upgrade around 14:00 UTC. Expect ~5 minutes of downtime. | 819 |
| 7 | On a network upgrade after November 9, asset trades in the API will include a field users: [buyer_address, seller_address] . This information is available via nodes anyway, and the goal of the API is to make the most important onchain data for traders easily accessible.
For those who want to test out the change, it is live for testnet spot. Testnet perps will be supported shortly in a network upgrade. | 822 |
| 8 | Minor: After the next network upgrade, the "onlyIsolated" field in perps meta response will be omitted when false. E.g. {"szDecimals":5,"name":"BTC","maxLeverage":50,"onlyIsolated":false} will be replaced with {"szDecimals":5,"name":"BTC","maxLeverage":50} | 815 |
| 9 | There will be a network upgrade around 10:30 UTC. Expect ~5 minutes of downtime. | 782 |
| 10 | There will be a network upgrade around 14:00 UTC. Expect ~5 minutes of downtime. | 891 |
| 11 | There will be a network upgrade around 14:00 UTC. Expect ~5 minutes of downtime. | 1 055 |
| 12 | There will be a network upgrade around 11:00 UTC. Expect ~5 minutes of downtime. | 1 195 |
| 13 | Builder codes are now available via the API. Builder codes allow builders to receive a fee whenever an order they send is filled. Builder codes currently only apply to perps. In order to use builder codes, the end user would first approve a max fee for the builder address via the ApproveBuilderFee action. Once this step is complete, future order actions may include an optional builder parameter: {"b": address, "f": number}. b is the address of the builder and f is the builder fee to charge in tenths of basis points. I.e. a value of 10 means 1 basis point.
For more details, see the docs: https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes or the python SDK: https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/examples/basic_builder_fee.py | 1 307 |
| 14 | There are some improvements to the testnet EVM block database which are not backward compatibile, so there will be a one-time pruning of blocks on the next testnet network upgrade. This does not affect the testnet EVM state, only historical block queries. | 888 |
| 15 | There will be a network upgrade around 10:30 UTC. Expect ~5 minutes of downtime. | 958 |
| 16 | 1. Reminder that Agent/API wallets now have expiration dates. API users should make sure to authorize new API wallets before expiration. See previous announcement for more details.
2. Transferring USDC between spot and perp wallets will now require a user signature. The new action is called UsdClassTransfer and is documented in the Python SDK. The existing SpotUser action will be discontinued after Oct 6 0:00 UTC.
3. The leaderboard info request is now at https://stats-data.hyperliquid.xyz/Mainnet/leaderboard and updated hourly. The existing leaderboard info request will be discontinued after Oct 6 0:00 UTC.
4. The vaults info request is now split between vaultSummaries info request and https://stats-data.hyperliquid.xyz/Mainnet/vaults. The vaultSummaries endpoint contains vaults less than 2 hours old, while https://stats-data.hyperliquid.xyz/Mainnet/vaults contains an hourly snapshot. For recent data on any specific vault, use the vaultDetails endpoint. The existing vaults info request will be discontinued after Oct 6 0:00 UTC. | 1 112 |
| 17 | There will be a network upgrade around 11:00 UTC. Expect ~5 minutes of downtime. | 789 |
| 18 | There will be a network upgrade around 11:30 UTC. Expect ~5 minutes of downtime. | 913 |
| 19 | Agent wallets (also referred to as API wallets) will start enforcing expiration times following the next network upgrade. After the network upgrade, existing unnamed and named agent wallets will expire 2 weeks or 90 days after the upgrade respectively. Those will also be the default durations for named and unnamed agent wallets respectively.
Agent wallets will expire within 1 hour after their expiration time, after which the nonce set associated with the agent wallet will be deleted. It is HIGHLY recommended to NOT reuse a deleted agent wallet as actions that were previously signed by that wallet may be replayed since the associated nonce set was deleted.
A custom expiration can be added to the ApproveAgent action by appending valid_until {timestamp} to the name field. The expiration can be at most 180 days in the future. | 992 |
| 20 | There will be a network upgrade around 07:30 UTC. Expect ~5 minutes of downtime. | 756 |
