US 12,443,952 B2
Management platform for community association MGCOne online platform and marketplace
Savitha Sathyan, Chicago, IL (US); and Jeyaranjan Sankarasivam, Chicago, IL (US)
Filed by Savitha Sathyan, Chicago, IL (US); and Jeyaranjan Sankarasivam, Chicago, IL (US)
Filed on Dec. 1, 2022, as Appl. No. 18/072,887.
Claims priority of provisional application 63/304,062, filed on Jan. 28, 2022.
Prior Publication US 2023/0245189 A1, Aug. 3, 2023
Int. Cl. G06Q 20/38 (2012.01); G06Q 10/0631 (2023.01); G06Q 20/40 (2012.01); G06Q 30/0601 (2023.01)
CPC G06Q 20/389 (2013.01) [G06Q 10/063112 (2013.01); G06Q 20/3821 (2013.01); G06Q 20/4014 (2013.01); G06Q 30/0609 (2013.01); G06Q 2220/00 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A system, comprising:
a processing component of a management server node connected to a plurality of entities over a permissioned blockchain network of an association management platform;
a memory component on which are stored machine language that when executed by the processing component, cause the processing component to:
receive, via an off-chain communication interface, an onboarding request from at least one entity off chain;
parse the onboarding request to derive a proposed role of the at least one entity;
broadcast the onboarding request and the proposed role to a plurality of minimum required entities using a smart contract protocol on the permissioned blockchain network;
receive a consensus response from the plurality of minimum required entities verifying the onboarding request;
responsive to receiving an onboarding consensus from the plurality of minimum required entities, onboard the at least one entity onto the association management platform by cryptographically recording, as a validated block entry, the entity's onboarding event and identity in the distributed ledger;
establish a digital identity and credentials for the entity, wherein the identity and credentials are recorded on the blockchain ledger and cross-referenced with role-specific metadata;
determine a role of the at least one entity based on the digital identity and credentials, including role authority and scope derived from the verified consensus; and
instantiate, based on a confirmed role, an application programming interface to provide access to a corresponding secure, role-specific user interface (UI) portal for the at least one entity.