stacks-core VS kanidm

下载地址：https://github.com/stacks-network/stacks-blockchain/releases

There are no plans for Bitcoin to stop being the anchor chain. Original plans included a sunset for PoX, but that is something the community will decide on, seems like that date will be extended by a lot or eliminated entirely. SIPs and discussions are around that get into this in detail. Ex. https://github.com/blockstack/stacks-blockchain/issues/2613

For details of the technical upgrade, please refer here.

Serendipity has occurred. At the launch of Stacks 2.0, the intent was for 2.1 to automatically go live at Bitcoin block 700,000. However, due to a bug this is not going to happen — the Stacks 2.0 chain will continue indefinitely(see#2507). But, we see this as blessing in disguise. We are strong believers in multi-stakeholder blockchain governance, and we believe that Stackers and miners should also have a say in when and how breaking changes occur — it shouldn’t be just the decision of developers. Therefore, we are going to take this opportunity to make sure that when the 2.1 upgrade is ready, it will only activate with the consent of the network.

Miners are also still in the process of adopting some recent node updates that will help them more reliably prioritize transactions with higher fees. Once those have been adopted thoroughly, this new wallet version should help transactions settle even more reliably.

here’s their github, don’t know exactly where in there the sortition is coded: https://github.com/blockstack/stacks-blockchain

That's the current plan. There's an open issue about whether or not to push it back, make it so users can vote to extend it, or just make it so that STX holders can police miners and make sure they don't discount-mine: https://github.com/blockstack/stacks-blockchain/issues/2613

Check this: https://github.com/kanidm/kanidm/ Maybe not production ready, but looks very promising

Kanidm is a identity management platform with a ldap compatible interface, sso and more. It's still young, but the author works on the 389 ldap server at suse, so knows how to build a secure ldap alternative :)

Here is the OAuth/OIDC issue: https://github.com/kanidm/kanidm/issues/278

They are talking here: https://github.com/kanidm/kanidm/pull/485 about being an IdP with support for OIDC, so once that is implemented you could probably federate to Keycloak (or any other compliant IdP).

Might be worth filing an issue, I'm sure they'd love the feedback.

Kanidm: A simple, secure and fast identity management platform\ (22 comments)

Kanidm, it might not sound as fun or exciting but this sound engineering driven by exceptional people. Similarly, concread.

saml-rs, creating a SAML IdP in rust, kind of spun out of trying to do it for Kanidm.

And now they employ one of the lead 389 Directory Server developers (now the default in SUSE instead of OpenLDAP which is is still available but is going to be depreciated). The same person is also the lead developer of Kandim, a new beta IDM that looks really promising (but is likely quite some time from being ready for enterprise production).