Allow custom recipient of freed coins

[benjaminpreiss]

I would like to extend the deweb smart contract to allow setting a different recipient of the coins locked in a deweb page.
Can someone give me directions on how this could be done?

I have located the code for the pages purge() call, but can't find the source for the balance() function:

DeWeb/smart-contract/assembly/contracts/deweb-interface.ts

Line 343 in e0f4f47

transferCoins(Context.caller(), balance());

Can someone give me a hint where I can find it?
Also, how would the alternate recipient's address ideally be stored?

Extending the smart contract this way (ideally not as a fork?) could for example enable offering fiat onramps for a deweb page registry, but without the need to kyc customers. Otherwise, a deweb page registry with anonymous fiat onramp could be used as a means for money laundering.

Looking forward to your thoughts!

[peterjah]

Hello!
Can you elaborate in what case you would like to set a different user to receive freed coins?
purge() function delete the website contract and its storage

Depending on the answer to the question above, you have 2 ways to set a new recipient address:

• Store it a the contract creation (put it in storage in the constructor)
• Pass the recipient address in function parameters when calling the method

Anyway its something that could be done in the standard contract as an optionnal feature!

All contract helpers and ABI are in this repo:
https://github.com/massalabs/massa-as-sdk

[benjaminpreiss]

Thanks for the answer!

The first approach would be what I want to do, as I dont want the owner of the smart contract to be able to adjust the recipient of the freed coins.

This is for money laundering protection on the anonymous deweb uploader I intend to build. People can anonymously onramp through my platform. To still be compliant with regulations, I need to make sure that this cannot be used for money laundering, hence the wish to adjust the smart contract.

It would be really cool if this would be merged on your end as an optional feature on the deweb uploader.
My question still remains though:

I have located the code for the pages purge() call, but can't find the source for the balance() function:
Can someone give me a hint where I can find it?

[peterjah]

Sorry but i still don't understand the usecase you describe.
For "freed coins" you mean the coins that are refund when a website is deleted ?

I don't get at what point your onramp system will implies to delete the deweb website.

About regulation compliance, you have the ability to make a website immutable. meaning it will be no more upgradable or deletable. maybe its what you are searching for ?

About the logic of your onramp dApp, i think it should be done in a dedicated SmartContract.

The balance() function is a direct call to the node state.
https://github.com/massalabs/massa-as-sdk/blob/431e73fe560d8f5aa91bd2937da8328e9aedef3f/assembly/std/coins/balance.ts#L9