2024 Analytics Results

[Andrei]

In February 2023, the Project Apario service was discontinued as a proof-of-concept (PoC) Software-as-a-Service (SaaS) Ruby on Rails (RoR) web application. This decision was not made lightly and nor was it easy to make. The SaaS RoR PoC was burdensome to maintain and costly to operate in 2020. The project faced Government Ordered Censorship as a result of choosing to release the JFK Assassination Files first.

There was significant demand for the JFK Assassination Files that were released on the service, and that was powered by a 12x bare-metal server private cloud infrastructure that was costing me around $6,000 per month to operate. In September of 2020, the name Project Apario was codified in the PhoenixVault idea, and while the Phoenix may have died in the ashes of the JFK Assassination Files once again being censored by the United States Government and its counterparts. I took the 12x bare-metal server infrastructure and optimized it down to a 6x bare-metal server cluster and removed all third-party SaaS dependencies from the topology. This reduced the OpEx of the service by $3,000 per month to $3,000 per month. This was much more manageable.

The enormous generosity of the community also supported and funded most of this services' expenses, and so while you help me with paying for the servers, I help you by writing the software and releasing the source code open source.

In February 2023 though, I was faced with a significant decision. The financial support provided to the project through voluntary contributions were less than 33% of the OpEx required to operate the servers, even at half capacity, half-cost and an optimized code-base provided double speeds over the 2020 release of the platform. The project was still not in the right direction.

Being a single person who has been behind the project since its inception in August 2019, under the name of Crowdsourcing Declas (unreleased by name as it was under development until PhoenixVault launched as the platform under a rebrand). I needed to replace the technology stack of the entire project. I couldn't support the old tech stack at the same time as building the new tech stack. I had to discontinue the project as it stood. It couldn't return as it was. Ever.

That being said, the Phoenix rises from the ashes.

2020, we thought that President Trump was going to get re-elected and we wouldn't be stuck with Joe Biden for 4 years and cackling Kamala Harris. In 2020, we thought that we were uniting with Q for the finale of the Great Awakening. Maybe you thought that. I was extremely busy building the PhoenixVault software. It's been 4 years. I needed to learn Go, and not just learn Go, but really grok it. I am still learning it. It's a complex language capable of doing a lot.

I work on this project part time. I spend my discretionary disposable income on the project. It costs me around $1200/month currently to run everything as it stands and the Raven Squad Army is supporting it with $15/month in support. Thank you for the support that you're continuing to show me. I am still extremely busy on the software and the code and my work can be seen on GitHub as its getting released.

For instance, I recently released go-passwd and go-checkfs on GitHub. These two packages are tiny, but pack a powerful punch. The go-passwd tool provides a safe way to audit a string before accepting it as a password. The go-checkfs provides an easy way to check.File and check.Directory by providing the path to either and the file.Options{} or directory.Options{}. One line provides you the ability to check for write permissions, ownership, read-only permissions, etc. Another package released was the verbose on GitHub. This provides me additional logging capabilities within Go, such as Tracef and TracefReturn and all normal *log.Logger methods like Printf and Println are wrapped around Sanitize and Scrub methods that use a SecretsManager to keep track of potential secrets being logged out into your log files. The Tracef related commands provide a stack trace of the thrown error message's call before creation, and the TraceReturn related methods will log a stack trace of the error, but return the error as an error structure for re-use throughout the application; but when the error is passed into the return of the func, a stack trace of the error is captured alongside the message of the error.

Last year I released the configurable package on GitHub, alongside the go-textee, go-gematria, and go-sema. All of these packages, while on their own may not seem to be connected to PhoenixVault or Project Apario, and thus why would you continue to sow seeds into my efforts? Well, these packages are dependencies to the apario-reader and apario-writer and in 2019 when I chose to use RoR for the PoC, it was because thats what was familiar to me and what had all of the dependencies that I needed. Go on the other hand is a much different technology stack and very different from Ruby on Rails. Therefore, in order to get the RoR PoC PhoenixVault out of my control and into your hands, it needed to be re-architected from the ground-up so it wouldn't cost you $6,000/month to operate. Now, a site like ElectionSelections.com can operate for $48/month! So, yeah, I could have kept with what was and become irrelevant, or I could adapt to the time and innovate a solution out of the problem I found myself stuck.

On December 17th the RLUSD stable-coin was released by Ripple, the company behind XRP. RLUSD will drive XRP like USDT drove Bitcoin (BTC) but without excessive fees like USDC / USDT. From personal experience, the Ethereum network would look something like this. I sent $100 USD ⇄ USDT (Tether) ⇄ ETH and I'd receive $66-$72 worth of ETH after paying $28-$33 in fees. With XRP, the $100 USD ⇄ RLUSD ⇄ XRP results in receiving $99.99 in XRP after paying $0.01 in fees.

On December 17th 2024, the $APARIO token was AirDropped to 434 XRP Wallets that set the $APARIO TrustLine by reserving 0.2 XRP. 86.6 XRP was reserved for the launch of the $APARIO token and the value of the token has reached a Market Cap of $1,268 in the first week since being launched! There are currently 529 TrustLines, increasing the demand of the token by an additional 95 XRP Wallets adding another 19 XRP leaving 105.6 XRP in the $APARIO Reserves.

The APARIO/XRP AMM Pool is providing over 451 XRP of liquidity. The APARIO/PHNIX AMM Pool is providing over 93 XRP of liquidity. The APARIO/GOPHER AMM Pool is providing over 136 XRP of liquidity. Finally, the APARIO/YEShua AMM Pool is providing almost another 17 XRP of liquidity. In total, there is over 697 XRP worth of $APARIO in AMM Liquidity circulating pools. At the current market rate of XRP, at $2.29; this results in $1,596.13 of circulating liquidity.

These liquidity pools are provided to you by me for a 0.693% transfer fee on the AMM Pool itself.

When you use the AMM pool to swap your APARIO tokens into XRP tokens, the pool will incur a fee of 0.693%. This fee is a result of a calculation performed on a signed transactions on the AMM Pool itself setting the pool transfer fee.

The average of the vote weight + proposed fee is calculated upon changes to the ledger and the current fee is 0.693% as a result of the above table.

The growth of the apario-reader while having no marketing, no social media campaigns, no outreach, etc. - has been growing month over month strongly even after being offline for 17 months between the discontinued PoC RoR PhoenixVault and the truly open-source decentralized apario-reader.

2025 will see the direct integration of the $APARIO token into the apario-reader and receive a re-brand and a new-logo under the name of PhoenixVault.

The future is going to be amazing!

Do you HODL $APARIO tokens?