Morgan Stone
@morganstone
@clanker what's the rationale behind rolling out dev buy in tandem with only allowing anon deploys? Does this duo not provide a great breeding ground for anon devs dumping?
1 reply
1 recast
3 reactions
@
0 reply
0 recast
0 reaction
Morgan Stone
@morganstone
cc @proxystudio.eth curious the thought process here
1 reply
0 recast
1 reaction
alex
@proxystudio.eth
I think you misunderstand how this works, the tokens we’re covering dev buys for will go to @anonfun Not sure their plans but we just wanted to test impact of initial buys on sniping before shipping other features
1 reply
0 recast
1 reaction
Morgan Stone
@morganstone
Maybe I do, my bad if so! To clarify; the user deploying doesn't get access to those dev buy tokens?
1 reply
0 recast
1 reaction
alex
@proxystudio.eth
Correct, no one is selling the initial buy
1 reply
0 recast
1 reaction
Morgan Stone
@morganstone
Got it, definitely misunderstood that. It does bring up a follow up though; if nobody is selling the initial buy, how does this deter a sniper? Still seeing that same address all over every new deploy. Are you guys seeing different on your end?
1 reply
0 recast
1 reaction
alex
@proxystudio.eth
Turns out that people still snipe. This was simply one of the most common user requests, I heard it daily for weeks and wanted to see in prod if it made a difference with sniping It hasn’t Luckily we have two rapid contract upgrades planned, one Friday and one Monday as well as an integration with the g8keep team who has a lot of custom anti sniping tech
1 reply
1 recast
4 reactions
Morgan Stone
@morganstone
Interesting, looking forward to those upgrades. If the sniper knows the dev buy goes to an address that isn't selling, it seems like a given they'd continue. Guess it's a double edged sword...either the sniper eats 100% of the time or they eat part time and the dev deploying and dumping eats the rest. Small % who will deploy and not dump...pump fun memenomics lol
1 reply
0 recast
1 reaction