Patience 辛抱 Pool

Cardano pool ticker: PATI
Pool ID: 42aebb6bd342c6ea6c5a9851c8af88de3804a38ff9b67dab4df1bc57

TG group: are not financial advice.

[Patience 辛抱 Pool @PoolPatience]

Welcome to Patience 辛抱 Cardano Stake Pool!

We are promoting a secure platform for staking Cardano ADA, dedicated to providing learning resources and helping the network grow for anyone who wants to be a part of it. Join us!

https://t.co/jYwPq43XYA

[Patience 辛抱 Pool @PoolPatience]

@CardanoSlacker @fencemakerNFT @MicheleHarmonic @LegionOfBrad Perhaps you might be aware of https://t.co/u7NU17SSgc ? Basically volunteer SPO db-sync access via API.

Aside from that and others mentioned, yeah, I don't think you can get a "light" client side w/ full node data integrity.

[Patience 辛抱 Pool @PoolPatience]

@OTG_WCat Always a fan of the Star Forge :)

[Patience 辛抱 Pool @PoolPatience]

@limbicnft @TobiasFancee @SebastienGllmt This was going to be my response.
That style of token can open many doors for utility, but we have seen past instances of malicious artifacts embedded alongside them.

Approached w/ appropriate care they have lots of potential, and ofc the native option will remain there too.

[Patience 辛抱 Pool @PoolPatience]

@Oussbenma @CardanoBook @IOHK_Charles @InputOutputHK I enjoyed your review, the book sounds promising and education on fundamentals is a problem we deal with every day with this space.

I might give it a look, thanks for the useful writing!

[Patience 辛抱 Pool @PoolPatience]

@Foxfan52 @KOALA_Steve If they submit accurate tips to @PooltoolI then orphans have a good chance of being captured there, sometimes on other sites.

Schedule hashes can be verified on Pooltool also (the pool's x/N blocks stat). Simple missed slot checks are not detectable, unfortunately.

[Patience 辛抱 Pool @PoolPatience]

@AllenWu29331265 You may also be able to use Koios for this, public db-sync API run by volunteer SPOs, similar to Blockfrost, so take your pick:

https://t.co/6YXC3SV6r4

I think you should be able to determine past luck using that information.

[Patience 辛抱 Pool @PoolPatience]

@jong_b_t @IOHK_Charles For informational purposes, the delay is somewhat random due to private leader schedule and VRF selection.

In a perfectly optimized system ie. 0 delay from Tx to block mint, avg. settlement time would be ~20 seconds at current block rate -- but w/ scaling could easily be faster.

[Patience 辛抱 Pool @PoolPatience]

@rodrigc6 @_KtorZ_ @Leo_Delegator @SebastienGllmt @stakenuts @matiwinnetou I think it's impossible to say how quickly you will notice a difference, but once these things are integrated the network will become significantly faster.

[Patience 辛抱 Pool @PoolPatience]

@rodrigc6 @_KtorZ_ @Leo_Delegator @SebastienGllmt @stakenuts @matiwinnetou Well, faster prop time could make larger blocks feasible if that is desired. Transit and so perhaps settlement may be modestly faster.

For dapps, depends on adoption of features. W/ the fork tools, a dapp Tx would consume less block space, significantly increasing throuput.

[Patience 辛抱 Pool @PoolPatience]

@nullHashPixel @KenricNelson You could create a new version that maybe broadcasts / records the events, but that could bloat things over time if nodes were required to keep track forever.

Dynamic topology may also make it a bit harder to get good info.

[Patience 辛抱 Pool @PoolPatience]

@nullHashPixel @KenricNelson There's some tracers that occur for forks: https://t.co/oWL4SRFsuY
w/ info eg. a peer host, reason etc.

The node keeps that data to itself and drops invalid forks, though.
It only sees events "near" it in topo, so you'd probably need a network for quality data collection.

[Patience 辛抱 Pool @PoolPatience]

@CryptoRev123 Good luck!

One thing about Python you may find of interest as a Cardano fan is that while it is object oriented (don't worry what this means yet), it can also be modeled in a functional manner.

This could help you understand the diff w/ eg. Haskell as you learn. Have fun! :)

[Patience 辛抱 Pool @PoolPatience]

@Jane14457995 @ADAFarmio @StakhanoviteIO @KpunToN00b I would also add to this discussion that relays add value to the network as a whole, as they function as validators and thus increase the validator node count in this system.

Eg. SPO who has a misconfig'd core often first discovers it when their own relay rejects their blocks.

[Patience 辛抱 Pool @PoolPatience]

@Jane14457995 @ADAFarmio @StakhanoviteIO @KpunToN00b You'd have to ask them individually. Up to them if they want to explain their topo.

Naturally it would reflect poorly to route eg. 5+ BPs through a single relay endpoint.

A claim to private relays is also difficult to verify as it's usually done for security / redundancy.

[Patience 辛抱 Pool @PoolPatience]

@ADAFarmio @Jane14457995 @StakhanoviteIO @KpunToN00b That is also possible, for sure.

Again due to lack of context, it is only possible to know what we know, which is that only one IP is associated publicly w/ the listed pools.

[Patience 辛抱 Pool @PoolPatience]

@Jane14457995 @StakhanoviteIO @KpunToN00b Overall it is important to understand what data like this means, especially if you care about decentralized infra.

You hear the term "single point of failure" a lot. This is one possible form it could take if there are not private relay networks behind these pools.

[Patience 辛抱 Pool @PoolPatience]

@Jane14457995 @StakhanoviteIO @KpunToN00b Homer mentioned prior information about P2P has suggested dynamic peering will only use such on-chain relay data at first.

This would mean these pools will only integrate P2P via these singular addresses. They could still make changes before then though.

[Patience 辛抱 Pool @PoolPatience]

@adasound_io @cardano_whale If you mean what I think you do, yes, liquidity contracts that can lock Ada and delegate it do wield a lot of potential power in terms of network control.

Protocols like LQ have advertised arbitrary staking whilst LPing etc, and I believe there are mechanisms to allow for this.