The Alerts methods send_message has a missing self argument. This method is not used anywhere in the code nor any examples, I guess it was never tested/used. Common Python mistake, can be easily spotted by running a static analysis. This type of analysis is recommended in Python as it is an interpreted language, it has no compile time before execution. So I recommend using pylance or flake8 to do so.

problem

I'm in your stack, touching your bits and playing with your stack and wrappers (fantastic work!!!)
However, to play with data I need to bridge to OP + create a smart margin account.

proposal

Enable user to instantiate with Kwenta(wallet_address=None, ...)
Handling sm_account to be None.

kwenta.py
ln 207: sm_account = self.get_sm_accounts()[0] if self.wallet_address else None

DoD

• user can interact with all queries and functionality that do not rely on an sm_account

Thank you for your repo,
I want to connect to testnet network then get price history and open-close position, but I got this error, can anyone help me fix that?
Code:

from kwenta import Kwenta

kwenta = Kwenta(
    network_id=420,
    provider_rpc="https://opt-goerli.g.alchemy.com/v2/...",
    wallet_address="0x...",
    private_key="0x..."
)

Error:

Traceback (most recent call last):
  File "test.py", line 3, in <module>
    kwenta = Kwenta(
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/site-packages/kwenta/kwenta.py", line 72, in __init__
    ) = self._load_markets()
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/site-packages/kwenta/kwenta.py", line 183, in _load_markets
    results = list(executor.map(self._load_market, allmarketsdata))
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/concurrent/futures/_base.py", line 619, in result_iterator
    yield fs.pop().result()
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/concurrent/futures/_base.py", line 444, in result
    return self.__get_result()
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/tuongnh/miniconda3/envs/trade/lib/python3.8/site-packages/kwenta/kwenta.py", line 116, in _load_market
    addresses["PerpsV2MarketSettings"][self.network_id]
KeyError: 420

Isolated margin read functions

• getMarkets
• getFuturesPositions
• getAverageFundingRates
• getDailyVolumes
• getIsolatedMarginTransfers
• getDelayedOrder
• getDelayedOrders
• getIsFlagged
• getIsolatedTradePreview
• getPositionHistory
• getTradesForMarket
• getAllTrades
• getFuturesTrades
• getOrderFee

Isolated margin write functions

• depositIsolatedMargin
• withdrawIsolatedMargin
• closeIsolatedPosition
• modifyIsolatedMarginPosition
• cancelDelayedOrder
• executeDelayedOffchainOrder

Smart margin read function

• getCrossMarginSettings
• getCrossMarginTransfers
• getCrossMarginAccounts
• getCrossMarginBalanceInfo
• getCrossMarginOpenOrders
• getCrossMarginTradePreview
• getCrossMarginKeeperBalance

Smart margin write functions (update with smart margin)

• approveCrossMarginDeposit
• depositCrossMargin
• withdrawCrossMargin
• submitCrossMarginOrder
• closeCrossMarginPosition
• cancelCrossMarginOrder
• withdrawAccountKeeperBalance

Hey team,

We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.

If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.

If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.

Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint, https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>

Need more support or have more questions? Feel free to reach out to [email protected]. We're here to help!

Cheers,

Paka