-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web3 Features #41
Comments
Why would devpool members swap via telegram instead of traditional DEXes which have way more tokens and liquidity compared to an individual devpool member?
You're right, this goes against the rollups feature. |
Long term Ubiquity will provide cards and remove EOA deps for the majority of our users, so at that point we are going to be basically a bank for those users. Those users need to be able to be able to move, swap and trade funds I'd imagine yeah? Since @0x4007 wants to go hard on account abstraction and remove literallly all crypto, we'd need to serve a UI and features to facilitate the moving and swapping of funds for our AA user base. But this logic can be used by EOAs too so we shouldn't restrict it to just AA users. Essentially we will become a wallet provider and so we need to provide utils to control their funds. This proposal would lay the ground work for that side of the DAO, without having to care about AA implementation rn we build to cater to user EOAs |
I think this can be used in 2026+ we need account abstraction implemented before we start solving problems for account abstraction. |
Roadmapped :))
It was my "low effort, long timeline contribution" is what I think @rndquu called it when he brought me onto the team. Ofc the landscape has since changed but my all the work I carried out is still there for it. |
The three below are going to be implemented throughout the org long term particularly when we go full account abstraction and have Ubiquity cards etc so perhaps we start to build such utilities into the telegram bot as a test run and then roll it out into UbiquityOS globally.
A) Under the hood swaps from [token] > My selection via DEX (most likely)
B) Choice between tokens in which the treasury has an active balance of (at that time)
/swap rndquu 150 UUSD 145 WXDAI
> Bot TG DM@rndquu, @keyrxng has sent you a swap request for: You Give: 145 WXDAI; You receive: 150 UUSD >> Accept | Decline | Counter
/trade 150 WXDAI 148 UUSD
148 being ourminOut
or throw, maybe we get more specific and use/sell 150 xyz -minReceived 148 abc
-/buy abc -maxIn 150 xyz
/setRewardToken 0x123
or/setRewardToken WXDAI
- prior to permit generation (with current permit flow not rollups) check user db (info registered via TG) and see token. If different, under hood swap it to user selected reward.All three of these allow for monetisation via a small fee for carrying out the transactions, which I'd feel is reasonable i.e if you want non-default behaviours and to fine-tune our network to suit you a flat rate 1% is charged on any swap and fed to the treasury, something like that.
This would require that we build a Mini App I'm sure so that we can get full web3 features (I have looked into it briefly, will deep dive if this is approved)
Alternatively, rapidly ship a UI that allows:
rndquu
and make the request forSwaps
then rndquu would receive a link to the same UI to confirm the request. We could do a lot with search params here I'm thinking.Trades
?/setRewardToken
is simple enough in theory, just a little unsure due to the direction of permits in general.@0x4007 @rndquu @gentlementlegen @zugdev @whilefoo @EresDev rfc
The text was updated successfully, but these errors were encountered: