Abstract: A nameserver receives a request to access a webpage from a client device. The nameserver generates a blockchain query based on the request for querying a domain registrar blockchain storing domain name registration data in smart contracts. The nameserver sends the first blockchain query to the domain registrar blockchain. In response to receiving a nameserver identifier from the domain registrar blockchain, the nameserver retrieves a DNS record for the webpage using the received nameserver identifier. The nameserver then provides information from the retrieved DNS record to the client device to allow the client device to access the webpage.

Abstract: A method of pollinating a plant: flying an unmanned aerial vehicle above the plant and generating a thrust that contacts the plant, that produces a sound pressure level of at least 6×10?5 Pascal at the plant, and that produces a frequency that induces the plant to release pollen.

Abstract: A multi-version database includes user-defined blockchain containers, where each of the user-defined blockchain containers is configured based on a type of data to be stored in a corresponding user-defined blockchain container. Each of the user-defined blockchain containers includes a set of one or more fields defined by a user. A command to write data to the multi-version database is received, where the command includes an identification of a first blockchain container of the user-defined blockchain containers, an identification of at least one of the set of one or more fields of the first blockchain container, and a value to write for at least one field of the set of one or more fields. A record is generated for the first blockchain container, the record including the value to write for the at least one field. A current state of the first blockchain container is then updated to include the record.

Abstract: A multi-version database includes user-defined blockchain containers, where each of the user-defined blockchain containers is configured based on a type of data to be stored in a corresponding user-defined blockchain container. Each of the user-defined blockchain containers includes a set of one or more fields defined by a user. A command to write data to the multi-version database is received, where the command includes an identification of a first blockchain container of the user-defined blockchain containers, an identification of at least one of the set of one or more fields of the first blockchain container, and a value to write for at least one field of the set of one or more fields. A record is generated for the first blockchain container, the record including the value to write for the at least one field. A current state of the first blockchain container is then updated to include the record.

Abstract: A user relational blockchain database includes a set of system-defined user blockchains and user-defined blockchains. The set of system-defined user blockchains includes metadata for managing the user-defined blockchains. Each user-defined blockchain includes a set of fields defined by a user and at least some of the fields are relatable. A command is received to write data that includes an identification of a first user-defined blockchain, a field, and a value. A new block is generated that includes the value set for the field. The new block is transmitted to a network of servers for consensus to add to the first user-defined blockchain. The new block is persisted to the first user-defined blockchain. A command is received to read data from the user relational blockchain database that includes an identification of the first user-defined blockchain and an identification of a field. The value corresponding to the field is accessed and returned.

Abstract: A user relational blockchain database includes a set of system-defined user blockchains and user-defined blockchains. The set of system-defined user blockchains includes metadata for managing the user-defined blockchains. Each user-defined blockchain includes a set of fields defined by a user and at least some of the fields are relatable. A command is received to write data that includes an identification of a first user-defined blockchain, a field, and a value. A new block is generated that includes the value set for the field. The new block is transmitted to a network of servers for consensus to add to the first user-defined blockchain. The new block is persisted to the first user-defined blockchain. A command is received to read data from the user relational blockchain database that includes an identification of the first user-defined blockchain and an identification of a field. The value corresponding to the field is accessed and returned.

Abstract: A method of pollinating a plant: flying an unmanned aerial vehicle above the plant and generating a thrust that contacts the plant, that produces a sound pressure level of at least 6×10?5 Pascal at the plant, and that produces a frequency that induces the plant to release pollen.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine may be independently maintained at each network node. The state machine may include a first state, a second state, and a third state. In the first state, which may be the steady state, a current cryptographic key may be used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key may still be used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key may be used for authenticating signatures of incoming packets. In the third state, the new key may be used for generating signatures for outgoing packets and either one or both of the old key and new key may be used for authenticating signatures of incoming packets.

Abstract: In a hitless manual cryptographic key refresh scheme, a state machine is independently maintained at each network node. The state machine includes a first state, a second state, and a third state. In the first state, which is the steady state, a current cryptographic key is used both for generating signatures for outgoing packets and for authenticating signatures of incoming packets. In the second state, which is entered when a new cryptographic key is provisioned, the old (i.e. formerly current) key is still used for generating signatures for outgoing packets, however one or, if necessary, both of the old key and the newly provisioned key is used for authenticating signatures of incoming packets. In the third state, the new key is used for generating signatures for outgoing packets and either one or both of the old key and new key are used for authenticating signatures of incoming packets.