aleixisp

you can set up in `send_transaction` method the `skip_confirmation=False`. Also there you can specify which signature status you want to trigger (Processed, Confirmed, Finalized). Hope it helps!

Jumping here. On my side that would be a breaking change, forcing fee payer at init. Glad to explore possible paths with y'all!

> This would be totally fine with me but I'm not sure how much pain it would cause others. This behavior makes it hard for me to build complicated transactions...

```python # Currently using metaplex Python SDK """https://github.com/metaplex-foundation/python-api""" from solana.rpc.api import Client solana_rcp_client = Client( endpoint=endpoint, commitment=Finalized, blockhash_cache=True ) """Initialize Token-init, Metadata-init transaction Solana.""" transaction, signers = \ deploy_token( client=solana_rcp_client,...

Hey, @andrewsomething I did had two contexts, yes. Is it mandatory to pass the `--context` flag alongside with the auth token every-time?.

Anywhere to see an example of the format for the proof? What are the steps to add other platform besides GitHub, Mastodon, Twitter and Telegram?