Abstract: One example method includes, in a node of a data confidence fabric (DCF), the node comprising hardware, obtaining, when available, a static confidence score for a lowermost layer of an infrastructure of the node, after a workload is orchestrated to the node, obtaining, when available, a workload confidence score, when the static confidence score and the workload confidence score are available, aggregating the static confidence score and the workload confidence score together to obtain an overall infrastructure confidence score, and applying, by the node, the overall infrastructure confidence score to data passing through the node.

Abstract: Generating policy-based confidence scores for data is disclosed. Data captured by a data confidence fabric is annotated when the data is created, mutated, transited or otherwise handled in the data confidence fabric. The annotations are weighted by a policy to generate policy-based confidence scores. The policy-based confidence scores are used in determining whether the data is sufficiently trusted for use by an application.

Abstract: Methods and systems are provided for assembly of coin components. Two or more coin components are received in an assembly station having at least two assembling members. The assembling members may be configured to form a chamber comprising the cavities and at least one assembling member may be movable over an assembling path. A merging force may be applied for assembling the coin components together to allow continuous production of joined coin components such that when the movable assembling member travels along the assembling path, one coin component locates within the other, thereby forming a coin assembly over a non-zero distance.

Abstract: A system and method for authenticating identity during a financial transaction based, in part, on dynamic biometric factors such as body temperature, heart rhythm, blood pressure, blood sugar, vein pattern, skin pore pattern, and voice recognition. The biometric values are captured, aggregated, and patterned over time to create a unique biometric profile. When a transaction is initiated, current biometric values are captured and compared to the biometric patterns, and a biometric authentication determination is made based on the results. An overall identity authentication score is generated based on a combination of the biometric authentication determination and other identity authentication determinations such as a purchase pattern authentication determination or a location authentication determination. An identity authentication determination is made based on the overall identity authentication score and communicated to the merchant.

Abstract: A system includes multiple sensors and, for each sensor, a respective sensor controller of multiple sensor controllers. Each sensor controller is configured to implement a respective decimation filter that is configured to generate a single output value from multiple input samples generated by a corresponding sensor of the multiple sensors. The system further includes a master sensor controller of the multiple sensor controllers, which is configured to generate a sync signal upon receiving a threshold number of input samples. Each sensor controller other than the master sensor controller is configured to monitor sync signals generated by the master sensor controller and to provide an output value generated from input samples upon determining that the master sensor controller generated a sync signal.

Abstract: A financial account proxy system receives a data packet from a first cardholder device. The data packet includes a limited use machine-readable code, receiver information corresponding to a second cardholder device, and one or more limitations. The machine-readable code, receiver information, and limitations are stored. The machine-readable code is associated with a primary account number of a financial account of the primary cardholder. A pre-authorization request message is transmitted to an issuer of the financial account, and pre-authorization details are received from the issuer. The limited use machine-readable code is transmitted to the second cardholder device. A transaction request authorization message is received from a POS terminal. The transaction request authorization message is associated with a transaction performed with the machine-readable code. The transaction request authorization message includes transaction details and the machine-readable code.

Abstract: A proxy or sidecar configured to connect an application to a data confidence fabric is discloses. The sidecar is configured to perform functions related to the transmission of data. As the sidecar intercepts communications to/from an associated application, the sidecar determines which of several functions to perform related to the transmission of data. In addition, the sidecar ensures that data confidence related operations and trust functions, as specified by the application, are applied to the data. Further, the sidecar identifies lineage when data is changed by an application.

Abstract: Invoking smart contracts in data confidence fabrics is disclosed. Trust functions are applied to data that is ingested into and/or flowing in a data confidence fabric. When a trust function is applied, a smart contract is invoked. The smart contract is configured to publish annotations to a distributed ledger that reflect the confidence information added by the trust function and to perform payment as a service such that the trust provider is paid. Publishing the annotations to a distributed ledger may be coupled or uncoupled to performing payment as a service.

Abstract: Global topics in distributed ledgers are disclosed. A distributed ledger is configured with a global topic whose identifier is publicized and well known. The global topic stores information about trust providers including topic identifiers and smart contract identifiers. Requestors can query the global topic to retrieve the information of specific trust providers. Once the information of the specific trust providers is known, the requestors can publish or write annotations and transactions to the distributed ledger. By associating the entries in the global topic with timestamps, requestors can reconfigure themselves automatically with updated trust provider information whenever a write to the distributed ledger fails.

Abstract: One example method includes connecting a digital wallet of a customer to an agent of a data confidence fabric, receiving, from an application, a request for performance of a trust function, by the data confidence fabric, with respect to customer data, processing the customer data by applying the trust function to the customer data, returning the data, after the processing, to the agent, creating annotations for the customer data, based on the trust function that was applied, transmitting the annotations, and a corresponding trust provider fee amount, to a smart contract, and when the digital wallet of the customer does not have adequate funds to cover the trust provider fee amount, obtaining funds from an alternate source of funding associated with the data confidence fabric.

Abstract: One example method includes connecting a digital wallet of a customer to an agent of a data confidence fabric, receiving, from an application, a request for performance of a trust function, by the data confidence fabric, with respect to customer data, processing the customer data by applying the trust function to the customer data, returning the customer data, after the processing, to the agent, creating annotations for the customer data, based on the trust function that was applied, upon successful execution of a smart contract, transferring a fee from the digital wallet to a trust provider associated with the data confidence fabric, and providing the processed customer data to another entity.

Abstract: One example method includes receiving, by a trust provider from a third party proxy, an indication that the third party proxy has instantiated a smart contract on behalf of the trust provider, connecting wallets of a customer to an agent of a data confidence fabric, in response to a request from an application, providing a trust service that includes processing customer data by applying a trust function to the customer data, creating annotations for the customer data based on the trust function, providing the processed customer data to a recipient, calling the smart contract using successive ones of the customer wallets until the smart contract is successfully executed, transferring, from the customer wallet that resulted in successful execution of the smart contract to the third party proxy, a trust provider fee, and transferring the trust provider fee from a third party proxy wallet to a trust provider wallet.

Abstract: Methods and systems for managing trust in data are disclosed. Generated data may be more or less reliable depending on the manner in which the data is generated. To identify a level of trust to have in generated data, information regarding the conditions under which data was generated may be provided along with the generated data. The added information may allow a receiver of the generated data to independently evaluate and ascribe the level of trust to have in the generated data. Different receivers of the same data may use different manners of evaluating the added information depending on their tolerance for risk in use of the generated data.

Abstract: One example method is performed in connection with a data confidence fabric. This method includes generating information about data as the data transits a data confidence fabric, ingesting the information, mapping the ingested information to a timeline, evaluating the timeline, based on the evaluating, generating a recommendation for an action concerning the data, and implementing the action in the data confidence fabric. In this method, the evaluating includes determining if any unexpected time gaps occurred as the data transited the data confidence fabric.

Abstract: Selective migration of a database in which one or more computing devices establish a creation specification for a snapshot of a subset of a source database of a source database management system (DBMS). The device(s) receive instruction to create the snapshot in accordance with the creation specification. The device(s) retrieve, in response to receiving the instruction to create, record(s) from the source database in accordance with the creation specification. The device communicates, via broadcast, the retrieved records to one or more creation listeners; and serializes, by each listener and in accordance with the creation specification, the broadcast records into the snapshot comprising the fragments and the parts.

Abstract: One method includes receiving a user-defined function, generating a binary based on the user-defined function, copying the binary to a target host where the user-defined function will run, in response to a lookup request, received from an API gateway based on a function invocation by a user, looking up the target host and a route, and returning, to the API gateway, a target host ID and the route, so as to enable the API gateway to request the target host to respond to the function invocation.

Abstract: One method includes obtaining a snapshot of a data confidence fabric billing manifest, broadcasting the snapshot to one or more nodes of the data confidence fabric, deploying, at the nodes, billing logic included in the data confidence fabric billing manifest, and executing the billing logic to obtain information concerning a trust service provided regarding data associated with the nodes.

Abstract: Executing functions in serverless platforms leveraging metadata is disclosed. Embodiments of the invention related to using metadata when placing and/or executing functions. The metadata includes request metadata, container or function metadata, node metadata, and/or data metadata. The metadata allows a function to be placed and executed in a manner that accounts for user intent, container requirements, node resources, and data location. Functions can be placed across different serverless platforms. Once the metadata is evaluated and a location is selected, a function is placed and executed at the selected location.

Abstract: A system includes multiple sensors and, for each sensor, a respective sensor controller of multiple sensor controllers. Each sensor controller is configured to implement a respective decimation filter that is configured to generate a single output value from multiple input samples generated by a corresponding sensor of the multiple sensors. The system further includes a master sensor controller of the multiple sensor controllers, which is configured to generate a sync signal upon receiving a threshold number of input samples. Each sensor controller other than the master sensor controller is configured to monitor sync signals generated by the master sensor controller and to provide an output value generated from input samples upon determining that the master sensor controller generated a sync signal.

Abstract: An electrode for a conducted electrical weapon may comprise an electrode body and an electrode head coupled to a first end of the electrode body. The electrode head may comprise one or more circumferential grooves. A filament may be stored in the electrode body and may be circumferentially wound into the one or more circumferential grooves to couple the filament to the electrode head. The electrode may comprise an absorber coupled to the electrode head. The absorber may comprise a core to provide rigidity and structure to the absorber. An impact spreader may be positioned forward the absorber. In response to an impact, the impact spreader may provide a force to the absorber to cause the absorber to expand radially outward.