# Feat/injective spot with delegation #6493

- Space: [Pull Request Proposals](https://snapshot.box/s:hbot-prp.eth.md)
- Author: 0xf3BD0db3c2ac17b6b3af8A1211cb3df274E5c62E
- State: Passed
- Voting type: Basic
- Start: 2023-07-19 13:25 UTC
- End: 2023-07-26 13:25 UTC
- Votes: 6
- Quorum: 315,656 voting power
- Open in Snapshot: https://snapshot.box/#/s:hbot-prp.eth/proposal/0xaf8fa07fbd40c0e92fed0b220c922b1f08416e2e8443e3dfd625ed30c89b6416

## Results

- For: 1,161,477.47 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

## Summary
Implementation of a pure Python (no gateway required) Injective spot markets connector to be used with delegated accounts.
Developer: Injective Labs team (https://injectivelabs.org/)
Documentation: https://api.injective.exchange/

## Rationale
With the intention of reducing issues when submitting transactions to the chain due to repeated or inconsistent sequence numbers we have created a new spot connector supporting delegated accounts. Delegated accounts means that the user will have the funds in one account (known as portfolio account or granter account) but all trading messages and transactions sent to the chain will be signed with a different account (known as the trading account or grantee account). To support this functionality the connector uses the Injective authz module.
With the new connector the user can have many Hummingbot instances trading using the same funds (the same portfolio account) but with a different trading account for each bot, ensuring that each Hummingbot instance will use independent accounts when sending transactions to the chain, and hence independent sequence numbers (eliminating with this the sequence number mismatch issues).

## Github Link
https://github.com/hummingbot/hummingbot/pull/6493

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

