LobsterDAO 🦞

13 Dec 2024 18:09

Can you not freeze the receiving address?

LobsterDAO 🦞

13 Dec 2024 18:09

What you can do is say if you “buyTokens” on current block you can’t “sellTokens” from same msg.sender / tx.origin on current block.

But then you can transfer to another address before - what pmr said.

The only solution that works I think - is have the tokens also be non transferable - or even better don’t even let users claim token until graduation. But then it’s a whole diff ux

LobsterDAO 🦞

13 Dec 2024 18:08

Nope, the receiving address gets frozen.

LobsterDAO 🦞

13 Dec 2024 18:07

if it becomes standard then frontrunning bot would just transfer tokens to a secondary address to complete the arb. Doesn't work.

LobsterDAO 🦞

13 Dec 2024 18:07

Sure but then it’s super permissioned and it’s not in the interest of the token launcher protocol to kill volume

LobsterDAO 🦞

13 Dec 2024 18:06

that's where the whitelist comes in

LobsterDAO 🦞

13 Dec 2024 18:06

nah, freeze it per address, not the entire token contract

LobsterDAO 🦞

13 Dec 2024 18:02

Means only one buy/sell tx goes through per block. Doesn t work then, most tx will fail

LobsterDAO 🦞

13 Dec 2024 17:31

Well if it’s open we just end up with free and fair competition, why would it be theatrics dao kind of thing?

LobsterDAO 🦞

13 Dec 2024 17:29

Honestly it's a nice to have for me as long as the L1 inbox is available.
It's a good revenue stream, so we will lend up with decentralization theatrics probably if they do move away from a single sequencer

LobsterDAO 🦞

13 Dec 2024 17:07

those are way more complete, so probably merging them into the current https://docs.privy.io/ page should suffice OwO

LobsterDAO 🦞

13 Dec 2024 17:05

I haven't read this section on the original docs, is that from somewhere else?

LobsterDAO 🦞

13 Dec 2024 17:01

Super helpful feedback. Had you had a chance to check this out? https://docs.privy.io/guide/server/wallets/delegated-actions/architecture

If so, I'll make sure we rework it, if not I'll work to surface it better.

But I hear you that where the tx is signed is different than who broadcasts it. To answer that question: it's up to developer to decide whether they want to use our rpc nodes to broadcast, or their own. So it's app specific

LobsterDAO 🦞

13 Dec 2024 16:58

https://l2beat.com/scaling/projects/arbitrum

LobsterDAO 🦞

13 Dec 2024 16:57

can't rug due to inactivity tho

LobsterDAO 🦞

13 Dec 2024 18:09

The receiving address takes the price risk for 1 block (or more, what ever parameter is chosen for this).

LobsterDAO 🦞

13 Dec 2024 18:08

Can't transfer it to a second address.

LobsterDAO 🦞

13 Dec 2024 18:08

It's only permissioned for a short time, so doesn't matter in the great sphere of things.

LobsterDAO 🦞

13 Dec 2024 18:07

Now every protocol that wants to build a bot / ux layer (like moonshot) has to do bd with the token launcher protocol

LobsterDAO 🦞

13 Dec 2024 18:07

And the freeze feature is temporary, only x blocks after launch, so it doesn't brick compatibility with anything after x blocks

LobsterDAO 🦞

13 Dec 2024 18:06

whitelist the main ones

LobsterDAO 🦞

13 Dec 2024 18:04

It’s not practical - would brick all telegram bots, for example

LobsterDAO 🦞

13 Dec 2024 17:44

A token standard that freezes a token for 1 block after each transfer to get rid of sandwich MEV. Whitelist router contracts to not be subject to the freeze. Let freeze feature deactivate after x blocks since sandwiching worst around token launch.
https://x.com/Madibaa08/status/1867608620076073368

Is that technically possible?
Say for something like PumpFun whose users are by construction only active on the token during the first few hours/days after its deployment. So them forcing such a standard on the industry could save their users quite a bit of money, no?

LobsterDAO 🦞

13 Dec 2024 17:31

Yeah this is an issue w docs discoverability we have to figure out. Thanks for the feedback

LobsterDAO 🦞

13 Dec 2024 17:26

Fair enough but I ll still support anyone shaming single sequencer chains. This is an anomaly and we the plebs should be vocal about it because it s the pleb’s best interest. Open the fucking sequencer.

LobsterDAO 🦞

13 Dec 2024 17:06

oh I see that there is a /server/ section there, I don't know why these docs are different from the ones I found

LobsterDAO 🦞

13 Dec 2024 17:02

Back to you asap with that -- we initially locked it down to passkey AFTER alt login, because we've found ~10-15% of users lose passkeys cross device. But ultimately, we will leave this up to the developer. Back asap!

LobsterDAO 🦞

13 Dec 2024 16:58

I'm trusting l2beat on this one (haven't checked the contract)

LobsterDAO 🦞

13 Dec 2024 16:57

I'll have to double check the L1 contract. I don't think it is upgradable or that param is modifyable

LobsterDAO 🦞

13 Dec 2024 16:56

or they can upgrade the exit window