Hello to our Loyal Wault Community.
By: Feed The Beast Official
Tags: Crypto, Wault Finance, Scam, Defi

Hello to our Loyal Wault Community. The circumstances of this announcement by the core team of Wault Finance have been long thought out as we were careful to gather all of the data in the most clear and

direct and visible form, as possible. We have recently discovered some information regarding our owner Creppy’s activities

that we find very alarming.

We strongly believe that each of us as individuals are free agents and able to draw our own conclusions.

So in this article we submit to you the preponderance of evidence we have found and allow you to come to your own particular viewpoint, in this regard. The first rule in crypto is do your own due diligence.

The evidence suggests that our owner, Creppy, has been actively seeking to deceive the community through various means available to him

as the primary writer of the code of Wault Finance and also as the clear owner of several other projects launched within our ecosystem, as per the uncovered data you will find listed below.

It is for this reason, and others yet to be discussed, that we are disassociating ourselves from any further connection direct or indirect with Wault.Finance.

We have chosen to go our separate ways and begin our own project launching on the KUCoin Community Chain. We severely regret not being able to bring this information to you sooner but as we continued our search more information surfaced, so we felt it best to wait until we had exhausted all aspects before bringing it to full light.

But before we touch upon some of the more datacentric info let us first explain some of the goings on that have also contributed to our disenchantment with the project, in general.

Firstly, all of the so far launched IDOs were completely unvetted by the core team, except Holder Finance. They were pushed on us at the last minute with some lame excuse from Creppy that he just “had this come his way and that we really needed to capitalize on the opportunity” and “no need to meet the team” and “that he was already doxxed with them” etc. etc., ad nauseum.

Our hands were tied even though we attempted to give him sound council asking him what the sudden rush was and if it was wise to move forward with such haste. This scenario played out over and over again first with Swirl cash and then Euler tools. And we were removed from discussions with Holder Finance even though we had brought the project to him through other legitimate sources we had in crypto land. After Holder launched we were

essentially removed from any further discussions with potential partners and were only aware of these inked contracts when the community was made aware. So, it was just as much news to us as it was to the community.

We kept on with the project thinking it was just a brief oversight and would improve over time. Sadly, it never changed even though we continued to ask that details be shared about partnerships and that the team deserved a full conversation with these other entities prior to officially connecting with them. Despite our continued attempts to illicit a response from Creppy, no explanation was ever given or even considered worth discussing

as it was just left unattended to in our Main Marketing Channel. This has gone on for the last two months since the migration. We understood that the team had grown larger and that decisions were being made outside of the purview of our core team chat but were never asked to participate in those other discussions or given even a courteous heads up. Even the migration came as news to us and this just shortly after finding out that Creppy had “accidentally” burned the team tokens in the Old Wault contract having sent them to the zero address. But, he offered a solution stating that it could all be sorted out if we just migrated with the Pancakeswap migration over to the new contract.

The team was in full support of this action excited about the opportunity to enjoy the fruits of our labor with team tokens being distributed. But still no opportunity for input was ever given to us in this matter as we found out about it after seeing the medium post published, detailing the coming change.

Once the team tokens came unlocked he simply told us that he wasn’t giving them to us and that he would probably just relock them. No discussion about this was entertained. No civil discourse and arriving at consensus with a trusted team, was considered. Rather, just a dictatorially decision made by Creppy, as in all things Wault, by this time. Very disappointing. And even if he had relocked them (which he clearly never did) they would have come unlocked again by now as he stated he would lock them for

another two months. This was mid April in which the tokens were technically made available to the team. When WEX was launched he did provide the team with an airdrop of tokens which is visible on the chain. But this portion paled

in comparison to the amount of tokens we were supposed to be allotted with WaultX, and was explicitly described in the Whitepaper as our due.

Another point of contention for team members was the fact that we were effectively cutoff from all key decision making since the migration. Apart from the occasional live AMA or interview handled by Marcelo, a sporadic quick video tutorial by Ken and the continued work with Regional Teams by Jimmy there was really nothing left of our connection to the ongoing development of the project even though we had grown the Wault community from the ground up. Having effectively developed it into a top trending project on the BSC through our early marketing efforts and existing connections. It is not overstating things to say that we were much to do with the early success of the project and the overall community engagement which made our project stand out and really feel connected as a Wault family. Once our project impact had been diminished, however, we felt little motivation or incentive to get back to that point having grown numb to the poor treatment from Creppy and general disrespect of our respective positions and core contributions. So we started looking to develop our own project and continue our evolution and overall reach in the world of crypto.

So, in some sense it was of less concern to us as we had been forced to move on in our minds due to the circumstances. But we knew what was happening was a disservice to the community. So we were conflicted in this. Little did we know how much Creppy was doing behind the scenes that should have led us away long ago to greener pastures and also given us an opportunity to expose all of his questionable activity, much earlier. We have always had the best interestsof the community in mind and are confident that the community has felt that from us, genuinely. But we feel that we have let you down, in this respect. And for that we again apologize to all of you. We, as investors ourselves, also feel very deeply the pain of betrayal and sympathize with every other holder of this once incredible token and ecosystem.

The below lists all of the data we uncovered about Creppy’s involvement with these other projects. We encourage you to come to your own conclusions about all of this information.

But as for us we are clear on what direction we intend to take.

First we started by checking if Wault.finance is leaking any data in the WHOIS of the domain name.

The WHOIS service provides data about the creator of the domain, where is the domain currently being hosted (Nameservers [which we will talk about later], Registrant Organization/Country, et).

We see that Wault.Finance has been registered at GoDaddy, so, we can see limited data, but enough to exploit future vulnerabilities:

Registrant Organization: Wault Finance

Registrant State/Province: Sofia

Registrant Country: BG

Nameservers:

Name Server: HARVEY.NS.CLOUDFLARE.COM

Name Server: LIZ.NS.CLOUDFLARE.COM (http://liz.ns.cloudflare.com/)

What do we know so far?

==================

-WaultFinance has been registered from an account with Bulgaria as origin, the owner (Creppy), could be/is of Bulgarian origin.

-WaultFinance is using Cloudflare to encrypt their traffic of their resource records (A[IPv4], AAAA [IPv6], NS [NameServers]), luckyly enough and “dumbyly” enough for Creppy and for us, the cocksucker forgot to filter his MX records thru Cloudflare, thus we found the Email Servers Wault is actually using:

wault.finance. 300 IN MX 20 mx2.zoho.eu.

wault.finance. 300 IN MX 30 mx3.zoho.eu.

wault.finance. 300 IN MX 10 mx.zoho.eu.

==================

At this point we find that Zoho is being used for Wault’s Email Servers, which is not yet relevant, but will be later.

Moving forward, we wanted to see if Creppy is actually operating many more projects under Wault’s umbrella and we found verifiable proof and will explain it in detail:

Wault’s Launchpad has been used by Wault Finance to boost new projects by providing a special opportunity to existing investors with the new launched projects.

We wanted to see if any of the Wault’s Launchpad sponsored projects was actually sharing the same WHOIS data and MAILSERVERS with Wault.

We took each project from Wault’s Launchpad and checked their WHOIS and Mailservers, and we found something very surprising:

WaultFinance

==========

wault.finance. 300 IN MX 20 mx2.zoho.eu.

wault.finance. 300 IN MX 30 mx3.zoho.eu.

wault.finance. 300 IN MX 10 mx.zoho.eu.

SwirlCash

========

swirl.cash. 300 IN MX 20 mx2.zoho.eu.

swirl.cash. 300 IN MX 30 mx3.zoho.eu.

swirl.cash. 300 IN MX 10 mx.zoho.eu.

Given the fact that SwirlCash was sharing the exact same Mailservers with Wault, we decided to perform a WHOIS query on Swirl.Cash to see if there is any potential leaking data, and there is:

Registrant Organization: Swirl Cash

Registrant State/Province: Sofia

Registrant Country: BG

Name Server: HARVEY.NS.CLOUDFLARE.COM

Name Server: LIZ.NS.CLOUDFLARE.COM (http://liz.ns.cloudflare.com/)

What have we deduced so far?

==================

⁃ Both domains have been registered under the same GoDaddy account.

⁃ WaultFinance and SwirlCash share the same MX Records, the same NS Records and the same WHOIS records.

⁃ WaultFinance and SwirlCash share the same owner.

The nest step in our mission was to check if we could find some similarities in Wault and Swirl’s code that we do not technically have direct access to but thanks to HTML and how browsers traditionally work, some output was visible.

Both Wault and SwirlCash using Wordpress as template for the website, among:

<title>App – Swirl Cash</title>

<title>App – Wault Finance</title>

We see the same entity in title tag: – which translates to: “-“ (without “ “)

In both websites we found the following call to a binance-wallet.png file, but both websites doing it differently:

https://app.wault.finance/binance-wallet.png -> SwirlCash Loading wault.finance link, Swirl loads an invalid link

https://app.wault.finance/bsc/binance-wallet.png -> WaultFinance version, Wault loads a valid link

None of Wault Launchpad’s projects (Euler.Tools, Investin, Hodler Finance) have actually HTML entities in their code or are loading binance-wallet.png, or are using the same MX Records (Mail Servers), or the same NS Records (name servers), nor are they registered in Bulgaria.

The final area that deserved attention in our mind was the WEXPoly sniper bot involved at the launch on Polygon that bought up much of the supply. We felt it necessary to rule out any potential wrong doing especially considering the discoveries already made. So we got to work looking into the transactions

and the timing of the adding of liquidity to see if there may be any possible connection between the two.

And low and behold we found just that. You may judge for yourself if there is causality, here. But it is our view that there is as per the timing of these things.

Here are the Transaction records for your own perusal.

https://polygonscan.com/tx/0xa99959b547da3b13f59e9ed522ee0169a9e57af00d7659a45a6bf7861c7c7f93

https://polygonscan.com/tx/0x1e2f34fdd8ed92b6af68b6e065bd81bdd5870da0e48a74a16d2b838193909508

The proxy account bought within the same block and we believe an insider job highly likely, as the adding of liquidity was done at the same block as the Bot purchased. And since we already had reason to start doubting Creppy’s word, on the basis of our prior findings, we arrived at the conclusion of collusion between the two entities.

It is, without a doubt, a shock to us all and we understand how you may be feeling at this time. As such, we have created a telegram group for anyone affected by this news to vent their frustration openly, ask questions, get clarification etc.

The telegram link is: https://t.me/WaultRefugeeCamp

We know there will be many questions regarding the integrity of the team. And we welcome them. Our ultimate goal is to bring some integrity back into the crypto space.

And expect if you follow us you will see that in evidence, over time.

Our research was conclusive enough to arrive at our decision. Let your own conscience and research guide you in yours.

Again, we invite you to our telegram group to ask your questions and receive the support you may be needing.

Here is that address again: https://t.me/WaultRefugeeCamp

We will also be sharing it out, as well as this medium post, in the Main Channel until we are banned from access, which may not be very long.

We wish you all well in your future in the world of Crypto which we still believe to be full of incredible opportunity and amazing friendships which at the end of the day makes all of this worth it.