Methods and systems are disclosed for a digital signature system using scalable and reliable servers. The system includes multiple frontend servers that are each in communication with multiple backend servers. A remote application server sends a signature request to one of the front end servers. The signature request includes at least two public keys that each have a different server identifier embedded in them. The backend server extracts one of the server identifiers and tries the signature generating process with the corresponding back end server. If that that backend server does not respond, then the frontend server extracts the server identifier from another public key and initiates the signature generation process with that backend server. In some systems, the remote application server has a predefined relationship with multiple frontend servers so that if one frontend server is down, the application server can communicate with a backup frontend server.

A computer-implemented method for maintaining crypto tokens of a first type. A smart contract from a distributed ledger defines a bonding curve being as a sequence of multiple curve segments. A creation or annul function of the smart contract may integrate a bonding curve starting from the current supply size to a new supply size to determine an amount of crypto tokens of a second type. The crypto tokens of the second type may be transferred to or from a pool associated with the smart contract, while crypto tokens of the first type may be transferred to a user or may be destroyed. The current supply size of first type tokens may be updated correspondingly.

In some examples, a system receives first measurements of data items used by a build server in building an executable program, the data items copied from a data repository to a storage partition that is separate from the data repository, and the storage partition to store the data items relating to building the executable program by the build server. The system determines, based on the first measurements and according to a policy specified for the storage partition, whether a corruption of the data items used by the build server in building the executable program has occurred.

Provided are a payment method and system through generation of a one-time payment-only number of a real card linked with an application, wherein in order to make payment safely by generating a one-time payment-only number every payment without leaving card information of a user in a provider's payment terminal or by using the generated one-time payment-only number, when a real card is linked with an application installed on a user terminal and the payment terminal recognizes the real card, a user signature input window, and transaction information about payment performed with a one-time payment-only number generated by a card company server are displayed on a screen of the application of the user terminal, and payment is performed when a signature of the user is input to the signature input window.

Systems and methods are disclosed herein for real-time digital authentication. According to some embodiments, a certification authentication method includes receiving a list of third party root certificates from a remote server, the list of third party root certificates including at least one association between a program configured to run on the computing apparatus and a public key for authenticating communication between the program and an associated server of the program. The method may also include authenticating the list of third party root certificates. The method may also include initiating a communication between the computing apparatus and the associated server and authenticating the communication with the associated server using the public key. Furthermore, the method may also include loading the program onto the one or more memories during a bootstrapping process in response to determining that the communication with the associated server is authentic.

Implementations generally relate to providence certificates. In some implementations, a method includes generating a first providence certificate digitally signed with a first private encryption key, where the first providence certificate is associated with a first component of a product, and where the first providence certificate provides a first predetermined assurance. The method further includes generating a second providence certificate digitally signed with a second private encryption key, where the second providence certificate is associated with the product, and where the second providence certificate provides the first providence certificate and a second predetermined assurance.

An electronic device using a division permission and an operating method thereof are disclosed herein. The electronic device includes a processor or a memory storing at least one instruction executable by the processor, and when the at least one instruction is executed by the processor, the processor receives a request for installing a first application on an electronic device, acquires a division permission information corresponding to a signature permission declared by the first application, applies the division permission information to a database, installs the first application. The division permission information may be used for the signature permission on a second application different from the first application.

System and method are described for creating and validating identities across multiple blockchains. According to an embodiment, a system uses decentralized resources to receive an enrollment request comprising entity information to create a multi-chain identity of an entity and create an account with a global identifier for the entity and one or more decentralized identities (DIDs), each associated with a cryptographic blockchain of a set of supported cryptographic blockchains. The system maintains a mapping of the global identifier and the one or more DIDs created, share the global identifier and the one or more decentralized identities in a digital wallet associated with the entity. In an embodiment, the digital wallet is implemented as an application to be run on a computing device associated with the entity. The digital wallet stores the global identifier, the one or more decentralized identities, and corresponding cryptographic keypairs associated with each of the one or more DIDs.

The disclosed embodiments relate to securely booting firmware images. In one embodiment, a method is disclosed comprising receiving, by a memory device, a firmware update; validating, by the memory device, a signature associated with the firmware update; copying, by the memory device, an existing firmware image to an archive location, the archive location storing a plurality of firmware images sorted by version identifiers; booting, by the memory device, and executing the firmware update; and replacing, by the memory device, the firmware update with the existing firmware image stored in the archive location upon detecting an error while booting the firmware update.

Various embodiments of the present application set forth a computer-implemented method that includes generating, based on a resource file stored at an endpoint device, a credential data packet for authenticating with a first application executing in a first network, where the resource file includes a set of encryption keys associated with a plurality of applications including the first application, and where the credential data packet is encrypted with a device key signed by the endpoint device, and the credential data packet is signed by an endpoint device management (EDM) key extracted from the set of encryptions keys included in the resource file, sending, by the endpoint device, the credential data packet to the first application via a trusted communication channel, and receiving, by the endpoint device and in response to the credential data packet, an authorization packet from the first application via the trusted communication channel.