Solana aims for 250-millisecond slots.
However, this does not eliminate the necessity of reservations.
It simply makes the timing more forgiving.
A delayed reaction becomes even more delayed.
A thread 🧵
There is Raiku Townhall happening today.
Don’t depart with catchphrases.
Depart with numbers.
The importance of three categories should be recognized:
- Coverage
- Miss paths
- Yield
They tell a lot more than any slide of any roadmap.
A thread 🧵
Primus PoR marker is designed to perform a feed check.
It does not perform the audit of the issuer.
Head to https://t.co/qTpPjGPPzj to check there.
A thread 🧵
..@xxiang_xie will be in Seoul this Sept
The key here is not the event.
The important point is what zkTLS enables.
A dapp is able to prove a single fact on an existing website.
It does not need your password.
It's quite expensive. It does not require the rest of your story data.
4 /
Check the dashboard for things that can be verified.
On-chain reserves.
Off-chain reserves.
The last time of proof timestamp.
If you wish to check whether it all is true, invite an auditor.
3/
Primus does not exist on the issuer's ledger.
It does not confirm the entity.
It does not confirm whether the API might provide wrong data regarding the balance.
Thus, incorrect feed is still just the incorrect feed.
2/
@primus_labs manifests two points.
It proves the TLS session reached the feed provided to it.
And it shows that the logic has matched those feeds.
Thus, it is all proved.
1/
It will show you the total reserve, backing ratio, and last verification date.
Thus, you will know when the last audit was done.
However, it does not mean you will learn whether the issuer's ledger is clean.
@raikucom 5/
Or did it arrive there later on a faster chain?
Confirmation indicates that execution has taken place.
The slot shows whether execution has taken place at an optimal time.
Solana aims for 250-millisecond slots.
However, this does not eliminate the necessity of reservations.
It simply makes the timing more forgiving.
A delayed reaction becomes even more delayed.
A thread 🧵
There is Raiku Townhall happening today.
Don’t depart with catchphrases.
Depart with numbers.
The importance of three categories should be recognized:
- Coverage
- Miss paths
- Yield
They tell a lot more than any slide of any roadmap.
A thread 🧵
@raikucom 4/
There are several possibilities:
• Wait for the next leader
• Resubmit with a tip
• Abandon the action
Once confirmation is received, check the slot.
Pose a basic query.
Was the transaction completed in the slot that you were trying to target?
@raikucom 3/
Adjust the strategy according to the price of the failure.
If you can have a miss, do what you usually do.
If you depend on a particular time period, make an advance reservation.
You should think of your fallback option.
@raikucom 2/
Not every confirmation means that there was a success.
The timing still matters.
If the liquidation happens one slot later, it can be a very different price.
The oracle price gotten after the dependent transactions are executed is still late.
@raikucom 1/
The principle of execution remains the same.
AOT aims at a particular slot.
JIT aims at the next leader that gets there.
Speeding up the block generation does not change those facts.
The difference is just in shortening the time period of the delay.
..@xxiang_xie will be in Seoul this Sept
The key here is not the event.
The important point is what zkTLS enables.
A dapp is able to prove a single fact on an existing website.
It does not need your password.
It's quite expensive. It does not require the rest of your story data.
There is the information flowing in Ethereum.
There isn't a Bank API information to provide.
Payroll information isn't hidden.
This gap in knowledge is highlighted by @Xavier_bham in Shanghai on September 22.
A thread 🧵
@xxiang_xie@primus_labs 5/
It does not store your credentials.
It does not expose the entire response.
It does not hijack the account.
The proof remains centered on the statement being proved.
@xxiang_xie@primus_labs 4/
The source changes.
The interface changes.
The proof process remains the same.
The value is in understanding the boundaries.
ZkTLS verifies what is received during an authenticated session.
@xxiang_xie@primus_labs 3/
This is how diverse applications can make use of the same underlying procedure.
Proof of Reserves can attest to reserve balances, without disclosure of full account data.
Pulse can make sure that a claim is valid while remaining the holder of the account.
@xxiang_xie@primus_labs 2/
zkTLS takes a different approach.
You visit the real website.
An attestor verifies the TLS session.
You prepare a proof for an assertion.
The login credentials stay with you.
The full page stays with you.
Just what you want to show advances.
@xxiang_xie@primus_labs 1/
Most existing approaches create tradeoffs
By linking an account, the app might be able to read anything in that session.
If you do a screenshot then you cannot reliably prove it has not been altered.
None of these is perfect, especially if you only want to check the one fact.
There is Raiku Townhall happening today.
Don’t depart with catchphrases.
Depart with numbers.
The importance of three categories should be recognized:
- Coverage
- Miss paths
- Yield
They tell a lot more than any slide of any roadmap.
A thread 🧵