Exiting FTM positions

I am exiting all my $FTM positions.

With turbulance on @FantomFDN, with it transitioning to its new token $S, I no longer know if $FTM will hold value, long-term.

I'm sad, because Fantom was a cute, cheap blockchain.

Too bad they got hacked.

Too bad I lost $69k in that hack.

Kujira Pilot launch of KART by premium: pop-quiz answer

#Cryptocurrency pop-quiz answer:

$KART launch on @TeamKujira Pilot happened in a flash.

• 45M $KART sold at launch
• ~ 492,570.00 $USK raised

Congratulations and «bon chance!» to all who participated.

Cryptocurrency pop-quiz: Fair market value $KART based on other Kujira Pilot launches

#cryptocurrency pop-quiz: $KART ... before the horse?

These are the token-sales on @TeamKujira Pilot, their launch price, and their current price:

• $NAMI,21.875¢,2.1651¢
• $WINK,0.5¢,4.5115¢
• $AQLA,25¢,4.438¢
• $BFIT,16¢,0¢

Interesting. 

Here are the charts of those tokens that are traded on @TeamKujira FIN

1. Which tokens increased in value after Pilot launch?
2. What were their ROIs and APRs since launch?

Given the above:

3. What is the fair-(or anticipated-)price of $KART using a-priori analysis?

• (answer)

Cryptocurrency pop-quiz: $KART sale

#cryptocurrency pop-quiz: $KART.

$KART is on sale on @TeamKujira PILOT for an opening price of 18.75¢ at 0% premium.

• There are 45M $KART for sale
• There are 148.02k $USK bids, average price: 0.99¢.

1. compute $KART-price at each premium %
2. compute remaining $KART, if any.
3. At each premium % there's a certain amount of $USK bid, meaning that there's a certain amount of $KART to-be-sold.

Currently, at 0% premium, there's 435 $USK bid, meaning, 2320 $KART will be sold there.

Compute amount of $KART sold at each premium %age, comme ça:

SO! Now you know the PRICE of $KART at each %age, and you know HOW MUCH $KART is sold at each %age.

Which means you know how much $KART remains.

4. Compute the %age at which $KART sells out, if any.
5. Compute THE LIKELIHOOD a 100 $USK bid by you will be filled at each %age.

• (answer)

Structured Data Schemata: don't be an idiot

I eff'n HATE drooling idiots who (don't) create schemata for uniform data-as-JSON from API endpoints.

{ "avalanche-2": { "usd": 31.49 },
   "bitcoin": { "usd":...

Anybody see the problem with this?

Why not:

{ "token-id": "avalanche-2",
  "quote": { "currency": "usd",...

HUH?

When you, the consumer, try to consume the above JSON (the one with VARIANT KEYS?!?!?) in a programatic-fashion?

You're going to have to hack the HELL around trying to define what a key is, BECAUSE THE KEY IS A VALUE, FFS!

Perverting JSON's VERY CLEAR structure is just stupid!

Maybe it's because I have a 25-year background in structured data and knowledge-engineering, but when you define your schema as:

"The key is the name of the token id"

instead of

"The key is 'token-id' because it's an eff'n KEY not an eff'n VALUE!"

Then you're an eff'n idiot.

Remember, kids, there's a difference between:

• metadata, or labels; and,
• data, or values.

If you call yourself a computer scientist, software engineer, or data scientist, you should know this.

And if you don't know this, stop calling yourself what you're not.

Postlude

Now, for my next rant:

Let's talk about people who put compound or composite values into (atomic) cells, so you have to CREATE A PARSER to ingest data FROM A DATABASE?!??? ... when they could have just as easily loaded each atomic value into its own (labeled/typed) cell?

Fun!

Rust pop-quiz answer: Configuring reading configuration files by git branches

#Rust pop-quiz answer to configuring reading configuration files by git branches.

code 

I've inlined a branch-parameter into reading REST resources. This came about whilst doing work on pivot-trading. 

Pivot pop-quiz: dictionary of coin gecko token IDs

#Rust pop-quiz 03

You see, when you complete the previous quizfos that the first two lines of pivots.csv are metadata:

• line 1: @coingecko token API ids
• line 2: token-symbols

Pair line 1 to line 2. Then query a token API id to get its corresponding symbol.

Here we see the @coingecko token API id fantom is for $FTM

• (answer)