Hi Remi

On Fri, Aug 29, 2025 at 08:35:54PM +0300, Rémi Denis-Courmont via ffmpeg-devel 
wrote:
[...]
> >+        },{
> >+            "guid": "ffmpeg-crypto",
> >+            "type": "other",
> >+            "address": "0x2f3900e7064eE63D30d749971265858612AA7139",
> >+            "description": "USDC on 
> >etherium/arbitrum/base/optimism/polygon, small amounts only, until we fully 
> >understand tax and accounting of this"
> >+        }
> 
> Does SPI controls this crypto-wallet? If not, then either:
> - the entity controlling the wallet is somehow not taxable and is 
> appropriating community funding,
> - the entity controlling the wallet is taxable and, on top of the above, it 
> is legally questionable, no matter how small the amount(s).
> 
> In other words, unless the answer is "yes", the only possible response is 
> "hard nack".

Ive sent a V2 of this patch without this wallet, but to awnser your questions

This is FFmpegs gnosis safe wallet, i have originally set it up
The wallet is controlled by the General Assembly of FFmpeg and SPI

And the General Assembly can change the person(s) who control the wallet
For example the GA could simply choose any people it wants
these people then could make a transaction. for example it could be setup as a 
2 of 3
multisig, so that 2 of 3 people have to agree on a transaction.

(of course once the GA does that, only these people can make future changes)

Currently the wallet is intended to only serve as a intermediate to move money
from crypto USDC to USD on SPIs/FFmpeg. This is not a taxable operation here
according to the tax adviser i have asked. But i still would like to limit
the use of this wallet until we are sure everything works in practice.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

You can kill me, but you cannot change the truth.

Attachment: signature.asc
Description: PGP signature

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org

Reply via email to