Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't sign transactions created on server. #344

Open
ironhacker opened this issue Jan 29, 2025 · 2 comments
Open

Can't sign transactions created on server. #344

ironhacker opened this issue Jan 29, 2025 · 2 comments

Comments

@ironhacker
Copy link

I'm attempting to sign grouped transactions with Pera created on the server using Python and algosdk. Looking at your code, it appears to expect a "from" field:

Pera.ts, line 225
const signer = algosdk.encodeAddress(txn.from.publicKey)

The transactions created using algosdk do not have a from field, but a sender field instead. Because these are group transactions, I cannot alter the transaction on the client without breaking the signature.

My current workaround is to access the wallet directly:

const peraWallet = await activeWallet.value.client
and sign using this wallet.

Wouldn't it be best to stick to the standard transaction format? One fix would be to add a signRawTransaction method, that would pass the transaction unaltered to the client.

@Contributordev
Copy link

Hi @ironhacker
Reach out to the official Support Portal to report your request and get more details by initiating a live chat with an agent through the chat button on the platform. Access the portal here: Support Page.

Note: Click the chat button to start a conversation with an agent for assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@ironhacker @Contributordev and others