Liquid Protocol - ETH (@ProtocolLiquid) header
Liquid Protocol - ETH (@ProtocolLiquid) profile picture

Welcome to 💧 Liquid Protocol — the pioneering platform for liquidity providers on the Ethereum network. Fully compatible with UNISWAP V2.

Bahamas
Joined July 2023
V4 is finally live on mainnet! We're reviewing what the next steps will be for the project. There are 2 main options, either a relaunch + push, or a push with the same contract. We're more inclined to the first one. The reason our liquidity wasn't relocked is that we're considering those options. We're gonna go hard once the utility season starts. Remember that V4 is only available on ETH chain, meanwhile V3 is available on all chains. $LP 💧
9
11
27
2,183
Hey everyone! We're offering a TESTNET version of LIQUID PROTOCOL V4! We're really close to having it work on ETH MAINNET. You can test it on the SEPOLIA TESTNET. Please remember that UNI-V3 is very different from UNI-V2. Once live on mainnet, we'll be, once again, the first service offering borrowed-liquidites for the UNI-V3 Protocol (LP's V4). We're also working on a guide on how to launch on UNISWAP-V3, since, remember, it's very different from V2 (hence why it was so hard to develop for us, too). There's been a few issues regarding the withdrawals of ETH using our contract, therefore MAINNET isn't live yet. However, this is not only proof of work, but a functional one. Try it out, at: liquidprotocol.io/app
13
8
1
33
3,076
$LP is now offering its services on 4 chains! These chains include: ETH BASE BSC ARB With the volume flowing in on #BASE, we could see a big step in adoption. Want to 'rent' liquidity on BASE? Use #LiquidProtocol $LP! To access our services, please check out our dapp at: liquidprotocol.io/app — anyone can access it! 200k has been done on buybacks until now. We're just getting started!
9
17
2
57
2,883
Our locker is live! You can now visit it through our app, at: liquidprotocol.io/app/lock/ We've even made an example of a locked liquidity, down below: liquidprotocol.io/app/lock/0… This is the beginning of the updates. We're sorry for the slight delay (truthfully, it has been 48h since Q1's end). According to our dev, multichain is coming next. However, multichain is not the update we're all focused on, but V4 is. The LP-V4 (UNISWAP V3) contract, as posted on March 20, is already working. We're trying to hide its functionality in a proxy contract in order for our utility not to be stolen. Nevertheless, in the case of our developers being unable to do so, we'd just launch the product with its functionality visible, just to get it out ASAP. Remember that, once LP V4 is done, we'll again be (even with the delays) the first project of the market to offer such service! So, no worries about staying on top on that regard! $LP #LIQUIDPROTOCOL
9
7
2
37
2,255
We're progressing with development! This shows a picture below of a transaction in which we were able to deploy and create a V3 pool in the same transaction. The new developer is also playing around with price ranges (since we need to make this easy to understand for the average user, as that's partially our job, besides the lending facility)
10
9
2
47
3,049
This is what the developer(s) have been working on lately: We understand things seem to be going slow, this is because our main developer was busy managing some stuff in his personal life (which I cannot mention, for the sake of his privacy). He should be back fulltime very soon, and gave us these pictures today. Sorry for the lack of updates, we don't like to just 'spam post'. I have some numbers about revenue which I'll present on Monday, at a similar time of this post (6-7PM UTC). You'll be impressed when you notice how much we made!
17
26
1
87
4,932
We've had a launch today borrow 5ETH for liquidity! Transaction: etherscan.io/tx/0x97f28b0b87… We're very happy to have such great teams working with our tool. Their coin is also performing extremely well up to the point where multiple influencers are calling it out as an 'alpha'. $LP deploys are cooking! Besides the aforementioned, it's important to note that our treasury is now sitting at a hefty ~690k (nice) value. 1M is coming soon, plus V4+locker updates will greatly increase our exposure and reach, since we'll be the one and only protocol to offer both UNI-V2 and UNI-V3 deploying, while also offering liquid lending on both of such.
39
53
3
126
14,075
We've had 4 launches in the past 8 hours! $LP's adoption is happening, and this is all before the wave of updates that's coming soon. Remember that V4 will include UNISWAP V3 Support. If we're getting this attention while providing an UNI-V2 service, which many do (although that's not what makes us unique, but the liquid lending is), eitherway, I'll leave it to your imagination, as to what we can achieve providing V3's support, which is an unexplored market, specially with the perk of no extra cost! These are the transactions and a quick reminder about it. Please read carefully! etherscan.io/tx/0xc7f29143ba… etherscan.io/tx/0x67842ef641… etherscan.io/tx/0x721b8e3cfb… etherscan.io/tx/0x721b8e3cfb… It's important to remind everyone that we're a platform which provides a tool as a service, we do not 'guarantee' any results on coins deployed from our protocol. Please always remember that! Deployed by $LP != Mooner. Deployed by LP means that the contract cannot be exploited, however the dev still has the freedom to do whatever they want. When a contract is both deployed by LP, and it borrows our liquidity, then the developer can't rug. Nevertheless, even if they can't rug, we can still have people abandon their projects, which is NOT in our control, nor can we limit with code, since that would be impossible.
18
36
1
105
9,518
Congratulations to teapawt.net/safudex! They've hit 3M marketcap earlier! We're very happy to have these type of hardworking & dedicated teams using our platform.
18
33
1
106
6,455
We've updated our socials on #etherscan. Besides looking clean, this is part of all the small improvements which are being done throughout time before the big release. After a chat with our developer, he has said that he wants to make the protocol 'as stable as possible', hence making it borderline impossible for new users to mess it up, even if intentionally. The aforementioned combined with the playbook will be crucial for adoption, since this will lift off some pressure from customer support, while also increasing the accessibility of information related to our product's usage.
12
23
1
81
4,232
The team's been working on our Locker's UI. Attached down below you can see a picture of it. Besides, these are the articles that we've purchased. You can use these to shill/attract non-DeFi people into our project! Yahoo Finance: finance.yahoo.com/introducin… Unfolded: unfoldedcrypto.com/introduci… Morning Star: morningstar.com/news/globe-n… Globe News: globenewswire.com/news-relea… and many more. The reason referrals have not been specified yet is because we need to make sure the difficulty of developing it isn't too time-taking for our developer, since V4 is our focus. Why is V4 our focus? Because that's where our revenue would not only be tangible before unlock, but also it'd be much easier to measure, plus we would be offering a service that nobody else ever has, once again, thus we expect it to be a game-changer.
13
22
76
4,650
Regarding the referrals ruleset, that post will be out tomorrow, alongside with articles (which we did get but did not post), hence making sure everything specified in the roadmap is done. Besides, the UI locker update is going great! Remember that slight delays are always due to happen because of the fact that the developer is working on this in real time, and as it is our own product, we have nowhere to take from or copy from, which of course, shows that it's ours, but also makes the progress very harsh. But we're committed to it. The UI itself has been improving, and I have attached a picture of it down below. Nevertheless, there are a few important topics to address as well. We've had an undeniable pullback lately, hence fud has appeared. It's not truly professional to address blatant lies, however, we can address some of the main ones: — 'Contract has an exploit/ can rug': We're audited by CERTIK. Unless someone is implying CERTIK themselves didn't find it, then this is a completely incorrect statement. Proof: skynet.certik.com/projects/l… —'Why borrow liquidity from you if you will rug it?' NO, wrong. Read the whitepaper. The process of removing liquidity from tokens which borrowed liquidity from our protocol is manual. This means that, unless you think we're evil (in which case, I cannot change your mind), we won't remove the funds in an improper time. The 'rules' have been set a week ago. Proof: rather.gitbook.io/liquidprot… —'you were in another project!' Firstly, there's no proof for that. However, we do have proof that this is the first project we do together, which will be tied to some of the pictures below. Proofs: Being happy about hitting 1M first (keyword) try. First try. Not second, not third. Our first token together. The 'wanted to quit' comes from them originally not wanting to work on a project because of market conditions, and just quitting defi instead.
14
19
4
76
5,872