Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Transaction service rejects transactions signed by proper delegates

See original GitHub issue

Describe the bug When POSTing against https://safe-transaction.gnosis.io/api/v1/safes/0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52/multisig-transactions with a transaction signed by a delegate with address 0x5E69fb460c9950F5AE90DafFc4C4F32EcafaCaA5, the Gnosis Safe Transaction service returns this reponse.

  ApiError: Error posting transaction: {"nonFieldErrors":["Sender=0x5E69fb460c9950F5AE90DafFc4C4F32EcafaCaA5 is not an owner or delegate. Current owners=['0x757280Bd46fC5B1C8b85628E800c443525Afc09b', '0x7321ED86B0Eb914b789D6A4CcBDd3bB10f367153', '0x6F2A8Ee9452ba7d336b3fba03caC27f7818AeAD6', '0x6E83d6f57012D74e0F131753f8B5Ab557824507D', '0x0Cec743b8CE4Ef8802cAc0e5df18a180ed8402A7', '0x74630370197b4c4795bFEeF6645ee14F8cf8997D', '0x99BC02c239025E431D5741cC1DbA8CE77fc51CE3', '0x48f2bd7513da5Bb9F7BfD54Ea37c41650Fd5f3a3', '0x7A1057E6e9093DA9C1D4C1D049609B6889fC4c67']. Delegates=set()"]}

To Reproduce Steps to reproduce the behavior:

Do POST on https://safe-transaction.gnosis.io/api/v1/safes/0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52/multisig-transactions

Won’t share the JSON since it has signed transaction data, but any valid transaction signed by the delegate is rejected.

Expected behavior Since the delegates endpoint for this safe returns 3 delegates, we expect that 0x5E69fb460c9950F5AE90DafFc4C4F32EcafaCaA5 should be able to POST to the multisig-transactions endpoint with no problem.

The fact that the error shows Delegates=set() indicates a regression in the transaction service that makes it believe this safe has no delegates. Which is incorrect.

Environment (please complete the following information):

Production
Ethereum chain id 1

Additional context This started happening a day ago. Before this we have been using this delegates for months and months without issue. Other safes my team owns do not have issues with delegates at this moment.

Issue Analytics

State:
Created a year ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

kx9xcommented, May 3, 2022

Aight, it finally went through, I am going to chock this up as being a transient issue.

0reactions

Uxio0commented, May 3, 2022

Like I understand that transactions that are successfully posted to the safe and are signed by a quorum of signers are executable by anyone.

Yes, that’s what I meant, that’s why I said there’s no big harm in sharing the payload for a transaction here

Top Results From Across the Web

TFM Part 4A Chapter 3000 - Treasury Financial Manual

Fiscal Service rejects forms with facsimile signatures or any evidence of erasures, corrections, or alterations. The delegator or designator block in Section IV ......

Universal Ethereum Delegated Transactions: No More ...

In short, delegated transaction, or "meta transaction" in blockchain is the type of transaction which performs an intended action on one ...

Trade Reporting and Compliance Engine (TRACE) - finra

FINRA member firms that delegate reporting to a third-party reporting intermediary must complete and sign the FINRA Transparency Services Participation ...

Understanding Delegated Access - Oracle Help Center

With the Delegated Access framework, a user can authorize another user to perform a task on their behalf by delegating access to perform...

chapter 151. regulation of money services businesses

(2) "Authorized delegate" means a person a license holder appoints under Section 151.402 to conduct money transmission on behalf of the license holder....