Vodeno

vodeno

Blockchain technology has permeated the modern world and is radically transforming the financial ecosystem.  Inspired by the dream of a decentralized and democratized method of dealing with financial services (to prevent recurrent overexertion and even outright malpractices by centralized financial institutions), blockchain technology has evidently made giant strides over the last couple of decades. From the creation of digital currencies, to their integration with the blockchain digital ledger (i.e, Bitcoin), to the introduction of smart contracts on blockchains (i.e., Ethereum), to the more recent introduction of decentralized exchanges (DEX) and the proliferation of decentralized applications (Dapps), blockchain technology has come a long way and it seems like it’s here to stay. However, though the dream of completely decentralized finance (DeFi) seems to have become very popular among tech enthusiasts who keep developing this infrastructure, it is yet to be achieved. So, more DeFi innovations are still being developed. Smart contracts are at the heart of the decentralized finance infrastructure as they manage the execution of transactions on the blockchain. Smart contracts play the important role of interfacing between the business and technological aspects of the blockchain as they are basically financial management protocols written in code format to regulate transactions on a decentralized record system like the blockchain. However, smart contracts on currently available and widely used blockchains like and , have a centralized management method which limits the current capabilities of blockchain technology. Bitcoin blockchain Ethereum blockchain Currently, smart contracts need to be triggered to function. This means that the smart contract code lies dormant on the blockchain until a specific event (e.g., transactions, update or configuration requests etc.,) are initiated by users of a blockchain and that causes the appropriate smart contract to awaken and execute tasks (i.e., triggering). This reactionary ideology results in blockchains being managed by centralized servers or bots (to coordinate the functioning of users’ requests and smart contracts), and this centralized control limits available blockchains because it makes them less secure and ultimately defeats the purpose of decentralization. Together with other factors like architecture and consensus protocol , this centralized management of smart contracts results in a well-established problem in blockchain technology known as , which basically means that blockchains currently have to sacrifice scalability, security or decentralization in their operation. Several approaches are being explored in an attempt to fix this trilemma issue but a breakthrough has recently been presented with the introduction of on a new blockchain known as Massa blockchain. ( ) proof of work vs proof of stake the trilemma autonomous smart contracts Autonomous smart contracts tackle this trilemma issue by being able to operate independently of external triggers, hence minimizing the need for a centralized means of managing them and therefore promoting all three factors of scalability, security and decentralization, instead sacrificing any. This was the main idea behind the development of Massa blockchain by three French scientists who have already released a beta version of the blockchain (testnet) for public access. We further explore autonomous smart contracts and their implications for the future of blockchain technology. Understanding the Trilemma Blockchain technology is currently limited by the trilemma, a long-established problem in computer science which involves the restrictions that security, scalability and decentralization place on one another. According to , this problem was first discovered by early computer scientists as the CAP (Consistency, Availability and Partition tolerance) theorem. The CAP theorem describes how decentralized data stores can only guarantee a maximum of two out of those three important features listed i.e., Consistency, Availability and Partition tolerance. Because a blockchain is essentially a decentralized data store, this CAP theorem also applies to it and this is what results in the trilemma. Cryptopedia.com The established blockchain premise that a public chain will have to choose between scalability, security, and decentralization in its operation is known as the trilemma. For instance, with well-known blockchains like Bitcoin and Ethereum, the tradeoff is mostly between scalability and decentralization. This problem is mostly due to the architecture of existing blockchains which validate on-chain activities using proof-of-work consensus protocol and also in a slow linear, node to node method in Bitcoin. Validation of activities (e.g., transactions) on a blockchain by consulting numerous nodes on the chain (i.e., consensus) is necessary to ensure security and decentralization. An issue then arises as more nodes are added to the blockchain because it takes more time to validate transactions with the nodes, which compromises scalability. However, fixing this problem by validating with fewer nodes will compromise decentralization and security (i.e., hackers can easily trick the few nodes and manipulate the blockchain). Hence, the trilemma. This already existing problem is further magnified by the centralized management of smart contracts through a server or centralized bots as the server can be hacked, bots can make mistakes, the centralized system has limited scalability and ultimately such centralized control limits the goal of decentralization. This tradeoff between scalability and decentralization in a blockchain is measured using the (NDC). The concept of autonomous smart contracts was specifically introduced to tackle this problem of decentralization and scalability in existing blockchains. The image below shows that with autonomous smart contracts, Massa blockchain has highly improved decentralization and scalalability when compared to Bitcoin blockchain, Ethereum blockchain and other blockchains. Nakamoto Decentralization Coefficient Hence, the introduction of autonomous smart contracts to solve the trilemma is a major game changer in the decentralization of blockchain technology. Solving the Trilemma A number of have been considered on different blockchains, in an attempt to solve the trilemma. Some of them are identified below. solutions Bitcoin introduced the lightening network which involves a second layer for off-chain transactions with multiple payment channels. Ethereum proposed a dual Proof-of-stake model with an execution layer for smart contracts and a consensus layer for transactions. Algorand is reported to have successfully solved the trilemma using its Pure Proof of Stake model The massa project is reported to have successfully solved the trilemma using autonomous smart contracts. Our focus here is on autonomous smart contracts which not only solves the trilemma but presents a new layer of automated decentralization in blockchain technology. The Massa Project reports that the Massa project was initiated in 2017 by Sébastien Forestier (CEO), Damir Vodenicarevic (development and technology leader) and Adrien Laversanne-Finot (company strategy leader). Their goal was to solve the trilemma by creating autonomous smart contracts. Beincrypto.com According to , the team accomplished this goal by creating a new blockchain (Massa) which combines consensus (proof-of-stakeconsensus gives paramount consideration to value staked on a blockchain in validating activities) and a multi-threaded blockgraph (facilitates parallel block creation), into an effective new system of blockchain functionality known as the blocklique. Then they developed autonomous smart contacts which are triggered by information stored onchain, and these characteristics enable their blockchain to run thousands of low energy cost operations within a second. massa.net proof-of-stake With autonomous smart contracts, the massa project succeeded in promoting decentralization and scalability in blockchains, with reporting it to be the first blockchain with up to 1,000 NDC, together with other perks like decentralized web hosting. The testnet phase of Massa blockchain was launched in 2021 and is reported to have successfully attracted over 7000 actively running nodes and crossed a throughput mark of 4,000 transactions per second. The mainnet (the official blockchain), is to be released with improvements on weaknesses in the testnet and targets a throughput of about 10,000 transactions per second. This is a massive step up for blockchain technology. Cryptonews.com Smart Contracts Versus Autonomous Smart Contracts According to , a smart contract is a decentralized program which executes business logic in response to certain events which trigger it. Smart contracts are generally developed by business professionals and programmers to manage activities like value exchange, service delivery, unlocking of protected content etc., on a decentralized data store like the blockchain. Due to this reactive ideology, smart contracts need continuous management for their operation and existing blockchains rely on centralized systems like a bot network or cloud infrastructure to automate them. However, this centralized management magnifies the trilemma problem. TechTarget.com Due to the obvious problem caused by centralized management of the smart contracts, the Massa team who developed autonomous smart contracts are to have asked this question; recorded " Why would you advocate for decentralization when you continue relying on obviously centralized means of interacting with your Smart Contracts?" Hence, they developed the idea of autonomous smart contracts to solve the trilemma issue through a new layer of decentralization. An autonomous smart contract can therefore be defined as a smart contract that doesn’t necessarily require external management for its automation i.e., it is capable of independent execution of a pre-assigned operations on the blockchain. It operates with blockchain data and can also request external information without need of additional management. Massa blockchain alone, currently has this smart contract functionality. This functionality is achieved through the storage of data alongside transactions and smart contracts on the blockchain. The data can then be accessed at any time by smart contracts for autonomous operation. Autonomous smart contracts are becoming more recognized in the decentralized finance world. The CEO of Dusa (an Automated Market Maker built with Massa blockchain) has this to say; " " Thanks to the autonomous smart contract and the blockchain hosting of our web application, we are able to offer the first 100% decentralized DeFi experience. Such technological innovations allow us to provide fully autonomous execution of our users' latent trading orders plus optimal liquidation management, all coupled with increased security for our users. Conclusion We conclude by analyzing the implications of autonomous smart contracts for the future of the blockchain. Considering how blockchain technology has been developed on an incremental basis, and the massive improvements autonomous smart contracts have been shown to make to blockchains, it is reasonable to state that existing blockchains like Bitcoin and Ethereum may also implement autonomous smart contracts to break loose of the trilemma. Though other methods of tackling the trilemma are available, autonomous smart contracts stand out because in addition to tackling the trilemma, they also promote decentralization which is the  fundamental principle for the creation of cryptocurrencies, in an automated way. Hence, while it is impossible to predict the future with certainty, autonomous smart contracts seem like a breakthrough technology which has come to stay, and will transform blockchain technology to a large degree.

Are Autonomous Smart Contracts the Future of Blockchain Technology?

How to Transition from Full-Stack Developer to Web3 Pioneer in 2022

The combination of our free, lightning-fast and always-on timestamp service and the easy to use cli tool, gets you started in a minute. Everything is built on top of open source components. Every build has a story to tell - Tamperproof provenance for your code and CI/CD pipeline What is trusted timestamping? is the process of securely keeping track of the creation and modification time of a document. Trusted timestamping Security here means that no one—not even the owner of the document—should be able to change it once it has been recorded provided that the timestamper's integrity is never compromised. uses its immutable open source database to provide this service that includes cryptographic verification and immutable data history. CodeNotary immudb CodeNotary Use Cases This timestamping service provides full immutability for all data ever written and unique data checksum ever stored including its history. As a trust level comes with the timestamp, you can change your mind over time (unsupport, untrust) without touching the code or binary. As the complete trust and timestamping history is stored for any digital identity (SHA-256 checksum), you can easily create workflows and decision trees in your CI/CD recipes. There are plenty of different use cases: Add a trusted timestamp to code Add an immutable timestamp to electronic signatures Seal the data integrity and your trust level at a given point in time Prove the existence of elecronic data at a specific point in time CI/CD integration - notarize all outgoing assets, authenticate all incoming Store provenance for you own sources Unsupport deprecated versions of your software and run update checks bases on the latest timestamp Revoke trust (untrust) at any time without the need to touch your code or binaries Trust or remove trust for digital assets and act on the status (within your script or pipeline) Simply timestamp files and sources to doublecheck at any time in the future if these are still the same (backup/restore) Simply request your API key and get started within a minute! This service was built using Open Source and to run free forever! Notarized assets information is stored in a tamperproof ledger with cryptographic verification backed by immudb, the immutable database. Obtain an API Key To provide access to our timestamping service a valid API Key is required. If you don't have one yet, simply signup here . CodeNotary Timestamp This API Key is bound to your email address and it's required during vcn login. Quick start 1. In case you use Linux or macOS, the quickest start is our install script: Installer bash <(curl https: //getvcn.codenotary.com -L) You can also download the latest release 2. to Login timestamp.codenotary.com vcn login --lc-host timestamp.codenotary.com # type your API key when requested
# or setting the API key
VCN_LC_API_KEY= in < Your-API-Key vcn login --lc-host timestamp.codenotary.com 3. Once you have an account you can start notarizing digital assets to give them an identity. Notarize (Timestamp) existing digital objects vcn n <file|dir: //directory|docker://dockerimage|git://gitdirectory> 4. You can use the command as a starting point. Authenticate digital objects vcn a <file|dir: //directory|docker://dockerimage|git://gitdirectory> : the timestamping and verification calculates a SHA256, so larger files might take a bit longer depending on your system. Tip For detailed , just run . command line usage vcn help Also published at https://dev.to/vchaindz/codenotary-free-trusted-timestamping-service-for-developer-158f

CodeNotary provides a Free Open Source Timestamping Service for Developers

Configuring Kerberos in nifi.properties The following key parameters for Kerberos are added to nifi.properties: Kerberos client authentication. If you want NiFi to use Kerberos for user authentication: nifi.kerberos.service.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.service.keytab.location=/path/to/nifi.keytab nifi.kerberos.service.principal is the Kerberos principal to be used by NiFi. Typically this is nifi/hostname@REALM.
_HOST is replaced by the name of the host on which NiFi is running.
nifi.kerberos.service.keytab.location is the path to the keytab file that contains the credentials for the principal. Kerberos for LDAP/Active Directory Authentication If you are using Kerberos in conjunction with LDAP or Active Directory for authentication: nifi.kerberos.spnego.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.spnego.keytab.location=/path/to/spnego.keytab nifi.kerberos.spnego.principal - SPNEGO principal used for authentication via Kerberos.
nifi.kerberos.spnego.keytab.location - path to the keytab file for SPNEGO. Kerberos for Inter-Node Communication If NiFi nodes in your cluster must also authenticate with each other using Kerberos: nifi.cluster.node.kerberos.principal=nifi/_HOST@YOUR_REALM
nifi.cluster.node.kerberos.keytab.location=/path/to/cluster.keytab nifi.cluster.nuster.node.kerberos.principal - the principal used by the cluster nodes to authenticate with each other.
nifi.cluster.node.node.kerberos.keytab.location - the path to the keytab file for the cluster nodes. Customize the JVM Environment for Kerberos krb5.conf You must make sure that the krb5.conf file (usually found in /etc/krb5.conf) is configured correctly and contains all the necessary parameters for your Kerberos realm. JVM Options Add JVM options to point to krb5.conf if required: java.arg.kerberos=-Djava.security.krb5.conf=/etc/krb5.conf This parameter can be added to the NiFi startup scripts (nifi-env.sh). Verify Kerberos Configuration Verify that Keytab files are available and contain the correct credentials.


Verify that all nodes in the NiFi cluster can obtain Kerberos tickets using the kinit command.


Verify that NiFi is successfully using Kerberos for authentication by running it and checking the logs for Kerberos-related errors. In a nutshell, these settings are needed if you need to consider Authentication: Kerberos provides a strong mechanism for authenticating users and nodes in the cluster. This means that each component, be it a user or another node, must prove its authenticity before accessing NiFi resources. In this way, the risk of unauthorized access is reduced. Security of inter-node communication: In a NiFi cluster where multiple nodes need to interact with each other, Kerberos ensures that all these interactions are secured. Each node must receive a ticket from the key distribution center (KDC) to prove its identity to other nodes. Encryption: Kerberos can be used in conjunction with SSL/TLS to provide encryption for data transmitted between cluster nodes and between users and NiFi. This protects data from interception and other attacks during transmission. Configuring Kerberos in nifi.properties Configuring Kerberos in nifi.properties The following key parameters for Kerberos are added to nifi.properties : nifi.properties Kerberos client authentication . Kerberos client authentication If you want NiFi to use Kerberos for user authentication: nifi.kerberos.service.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.service.keytab.location=/path/to/nifi.keytab nifi.kerberos.service.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.service.keytab.location=/path/to/nifi.keytab nifi.kerberos.service.principal is the Kerberos principal to be used by NiFi. Typically this is nifi/hostname@REALM. _HOST is replaced by the name of the host on which NiFi is running. nifi.kerberos.service.keytab.location is the path to the keytab file that contains the credentials for the principal. nifi.kerberos.service.principal is the Kerberos principal to be used by NiFi. Typically this is nifi/hostname@REALM . nifi.kerberos.service.principal nifi/hostname@REALM _HOST is replaced by the name of the host on which NiFi is running. _HOST nifi.kerberos.service.keytab.location is the path to the keytab file that contains the credentials for the principal. nifi.kerberos.service.keytab.location Kerberos for LDAP/Active Directory Authentication Kerberos for LDAP/Active Directory Authentication If you are using Kerberos in conjunction with LDAP or Active Directory for authentication: nifi.kerberos.spnego.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.spnego.keytab.location=/path/to/spnego.keytab nifi.kerberos.spnego.principal=nifi/_HOST@YOUR_REALM
nifi.kerberos.spnego.keytab.location=/path/to/spnego.keytab nifi.kerberos.spnego.principal - SPNEGO principal used for authentication via Kerberos. nifi.kerberos.spnego.keytab.location - path to the keytab file for SPNEGO. nifi.kerberos.spnego.principal - SPNEGO principal used for authentication via Kerberos. nifi.kerberos.spnego.principal nifi.kerberos.spnego.keytab.location - path to the keytab file for SPNEGO. nifi.kerberos.spnego.keytab.location Kerberos for Inter-Node Communication Kerberos If NiFi nodes in your cluster must also authenticate with each other using Kerberos: nifi.cluster.node.kerberos.principal=nifi/_HOST@YOUR_REALM
nifi.cluster.node.kerberos.keytab.location=/path/to/cluster.keytab nifi.cluster.node.kerberos.principal=nifi/_HOST@YOUR_REALM
nifi.cluster.node.kerberos.keytab.location=/path/to/cluster.keytab nifi.cluster.nuster.node.kerberos.principal - the principal used by the cluster nodes to authenticate with each other. nifi.cluster.node.node.kerberos.keytab.location - the path to the keytab file for the cluster nodes. nifi.cluster.nuster.node.kerberos.principal - the principal used by the cluster nodes to authenticate with each other. nifi.cluster.nuster.node.kerberos.principal nifi.cluster.node.node.kerberos.keytab.location - the path to the keytab file for the cluster nodes. nifi.cluster.node.node.kerberos.keytab.location Customize the JVM Environment for Kerberos Customize the JVM Environment for Kerberos krb5.conf krb5.conf You must make sure that the krb5.conf file (usually found in /etc/krb5.conf ) is configured correctly and contains all the necessary parameters for your Kerberos realm. krb5.conf /etc/krb5.conf JVM Options JVM Options Add JVM options to point to krb5.conf if required: krb5.conf java.arg.kerberos=-Djava.security.krb5.conf=/etc/krb5.conf java.arg.kerberos=-Djava.security.krb5.conf=/etc/krb5.conf This parameter can be added to the NiFi startup scripts ( nifi-env.sh ). nifi-env.sh Verify Kerberos Configuration Verify Kerberos Configuration Verify that Keytab files are available and contain the correct credentials. Verify that all nodes in the NiFi cluster can obtain Kerberos tickets using the kinit command. Verify that NiFi is successfully using Kerberos for authentication by running it and checking the logs for Kerberos-related errors. Verify that Keytab files are available and contain the correct credentials. Verify that Keytab files are available and contain the correct credentials. Verify that all nodes in the NiFi cluster can obtain Kerberos tickets using the kinit command. Verify that all nodes in the NiFi cluster can obtain Kerberos tickets using the kinit command. kinit Verify that NiFi is successfully using Kerberos for authentication by running it and checking the logs for Kerberos-related errors. Verify that NiFi is successfully using Kerberos for authentication by running it and checking the logs for Kerberos-related errors. In a nutshell, these settings are needed if you need to consider Authentication: Kerberos provides a strong mechanism for authenticating users and nodes in the cluster. This means that each component, be it a user or another node, must prove its authenticity before accessing NiFi resources. In this way, the risk of unauthorized access is reduced. Authentication : Kerberos provides a strong mechanism for authenticating users and nodes in the cluster. This means that each component, be it a user or another node, must prove its authenticity before accessing NiFi resources. In this way, the risk of unauthorized access is reduced. Authentication Security of inter-node communication: In a NiFi cluster where multiple nodes need to interact with each other, Kerberos ensures that all these interactions are secured. Each node must receive a ticket from the key distribution center (KDC) to prove its identity to other nodes. Security of inter-node communication : In a NiFi cluster where multiple nodes need to interact with each other, Kerberos ensures that all these interactions are secured. Each node must receive a ticket from the key distribution center (KDC) to prove its identity to other nodes. Security of inter-node communication Encryption: Kerberos can be used in conjunction with SSL/TLS to provide encryption for data transmitted between cluster nodes and between users and NiFi. This protects data from interception and other attacks during transmission. Encryption : Kerberos can be used in conjunction with SSL/TLS to provide encryption for data transmitted between cluster nodes and between users and NiFi. This protects data from interception and other attacks during transmission. Encryption

Kerberos + Ni-Fi = Secure

Is Your Apache Ni-Fi Ready for Production?

167 Stories To Learn About Developer Tools

Image via numomo.com There seems to be no end in sight when it comes to the digitization of our modern world. With social media, e-commerce and even self-driving cars, there doesn’t seem to be a limit in site to these exciting and incredibly advanced developments that bring a variety of convenient services to our current society. Cryptocurrency is yet another variation of technological enhancement within the 21st century that has caught quite a bit of attention since its creation. What is Cryptocurrency? If you haven’t heard by now, is a digital currency that is decentralized, unlike banks, and is . Bitcoin, the first and most popular cryptocurrency was invented in 2008 by an unknown individual that goes by the alias of Satoshi Nakamoto. cryptocurrency encrypted Since 2008, over 5,000 cryptocurrencies have entered the market and that number only seems to increase as more and more people are beginning to invest in them. Similarly, to the asset of gold and oil, there is a limited number of cryptocurrencies you can buy. So if you were wondering how a decentralized currency with no authority accumulates value, that is how. The lower the the higher the value of the currency. supply Now one may be wondering, “how does one keep track of these digital currency purchases and sales?” The answer to that would be blockchain. is an open, distributed ledger that records transactions in code. Think of this as a checkbook that’s distributed across countless computers around the world keeping track of every crypto transaction you’ve made. Blockchain Image via culturepledge.com How Does Crypto Fit Into Fashion? Crypto-fashion is digital fashion that can be traded and authenticated through the use of blockchain (a data structure that holds transactional records and ensures security and decentralization). Due to the pandemic, the conversation and genuine reliance on technology has accelerated. Whether it be looking to invest in cryptocurrency for expanding one’s wealth, or completely transferring the world of fashion to a virtual experience instead of a tangible one. It is no surprise that crypto has been linked to the fashion industry as of late. This emerging sector of fashion is still under development and uncharted territory for the majority however, it serves as an opportunity for designers and digital creators to bring a new identity and artistic purpose for the industry. Blockchain technology aids designers in maintaining ownership over their creations and manages those who want to obtain it without being ripped off. Crypto Fashion Week It wouldn’t be right to have this newly emerging sector of the fashion industry without a spectacular event to reveal to society what the future of design holds and where innovation is taking us. Crypto Fashion Week presents a comprehensive overview of the exciting, emerging sector of digital fashion. Crypto fashion week is bringing to the forefront a variety of digital designers who are creating luxurious designs for the pleasure of virtual and augmented reality. Image via voguebusiness.com DressX One of the many companies participating in the very first Crypto Fashion week was DressX. DressX was founded by Daria Shapovalova and Natalia Modenova in March of 2020. DressX is the first International digital fashion multi brand retailer that carries digital fashion collections, it’s only right that they be included in the first ever Crypto fashion week. DressX seeks to disrupt the fashion industry’s manufacturing traditions by not physically producing at all but creating a digital design that can be imputed into any augmented reality setting. Hoping to address and solve a portion of fashion’s sustainability issue, DressX aims to show that clothing can just exist as digital possessions instead of tangible ones. Gif via giphy Auroboros In addition to DressX, UK label Auroboros also made their Crypto Fashion week debut this year. Auroboros is a luxury label that produces and designs physical couture, as well as digital-only ready-to-wear pieces in the name of sustainability and innovation and is the first fashion house to do so. Founded by  Paula Sello and Alissa Aulbekova in 2020, the founders saw an opportunity in the midst of a pandemic to address the longstanding issues of waste and sustainability through the merging of crypto technology and fashion and is the first to ever do so. Image via gothammag.com Where Does Luxury Crypto Fashion Week Go From Here? While relatively new and extremely young, Crypto Fashion Week has wasted no time in demonstrating the intriguing and innovative ways that helped keep the industry moving forward. Crypto fashion week is an event that serves as a platform providing visibility to viewers of a more sustainable and ethical option when it comes to participating in the consumption of luxury fashion design. While luxury fashion and crypto technology is off to a great start in this new sector of the industry, they have merely scratched the service to what means they can serve consumers. As of right now, the extent of crypto fashion mainly serves designers and creators. Due to crypto fashion, designers have more autonomy over their designs than ever before. With blockchain providing protection for unalterable proof of creation, trademarks and licenses, designers have the capability of creating without having the worry of their work being taken without being compensated for. However, the question remains, how can crypto fashion further evolve to serve a larger consumer base? Beyond being an outfit for your virtual reality character or an investment, what other interactive channels can crypto fashion operate on in the near future?

Crypto Meets High Fashion

is for systems and applications. immudb lightweight, high-speed immutable database With you can track changes in sensitive data in your transactional databases and then record those changes indelibly in a the tamperproof immudb database. immudb This allows you to keep an indelible history of, say, your debit/credit transactions. immudb is open source under the , and can be found here (there is also a more comprehensive documentation): Apache v2.0 License https://github.com/codenotary/immudb Traditional transaction logs are hard to scale, and are not immutable. So there is no way to know for sure if your data has been compromised. You can find an example video here: https://www.youtube.com/watch?v=g7msV9NcwNA&t=1s How it works As such immudb provides , of what happened to your sensitive data, even if your perimiter was compromised. immudb provides the guarantatee of immutability by using internally a . unparalleled insights retro-actively Merkle tree structure immudb gives you the same of the integrity of data written with like classic blockchain without the cost and complexity associated with blockchains today. cyrptographic verification SHA-256 immudb has 4 main benefits: . You can only add records, but . immudb is immutable never change or delete records data stored in immudb is , like blockchains, just without all the complexity and at high speed. cryptographically coherent and verifiable Anyone can get . Wether in node.js, Java, Python, Golang, .Net, or any other language. It’s very easy to use and you can have your immutable database running in just a few minutes. started with immudb in minutes Finally, immudb is . You can run it , or in the and it’s completely free. immudb is governed by the Apache 2.0 License. Open Source on-premises cloud immudb runs on , , , and , among other systems derived from them, such as and . Linux FreeBSD Windows MacOS Kubernetes Docker Getting started You can either build Docker images based on the Dockerfiles in the GitHub repository for the most common architectures or use the prebuild ones on Dockerhub for Linux. immudb Dockerhub docker run -it -d -p 3322:3322 -p 9497:9497 — name immudb codenotary/immudb:latest standalone Binaries If you want to build the yourself, simply and run one of the following commands based on your operating system. binaries clone this repo GOOS=linux GOARCH=amd64 make immudb-static GOOS=darwin GOARCH=amd64 makeimmudb-static GOOS=windows GOARCH=amd64 make immudb-static # Linux # macOS # Microsoft Windows Then you can run immudb the immudb server ./immudb ./immudb -d # run immudb in the foreground # run immudb in the background install immudb as a service ./immudb service immudb install ./immudb service immudb status ./immudb service immudb stop ./immudb service immudb start # install immudb service # check current immudb service status # stop immudb service # start immudb service The immud linux service is using the following defaults: user: immu group: immu configuration: /etc/immudb data: /var/lib/immudb logs: /var/log/immudb Service Port: 3322 (immudb) Prometheus Exporter Port: 9497 Performance As immudb is often compared to Amazon QLDB, we did a performance benchmark using a simple demo application to write data (without using any unfair optimization). Test setup: 4 CPU cores Intel(R) Xeon(R) CPU E3–1275 v6 @ 3.80GHz 64 GB memory SSD Prometheus and Grafana monitoring immudb has a built-in prometheus exporter that publishes all metrics at port 9497 (:9497/metrics) by default. When running a Prometheus instance, you can configure the target like in this example: - job_name: 'immudbmetrics' scrape_interval: 60 s static_configs: - targets: ['my-immudb-server:9497'] There is a Grafana dashboard available as well: https://grafana.com/grafana/dashboards/12026 Common Use Cases We already learned about the following use cases from users: use immudb to immutably store every update to sensitive database fields (credit card or bank account data) of an existing application database store CI/CD recipes in immudb to protect build and deployment pipelines store public certificates in immudb use immudb as an additional hash storage for digital objects checksums store log streams (i. e. audit logs) tamperproof No programmer? Actually in case you’re not a programmer but still want to use immudb just to play around or within scripts, you can use immuclient. GOOS=linux GOARCH=amd64 make immuclient-static GOOS=windows GOARCH=amd64 make immuclient-static # Linux # Microsoft Windows In case you have no idea how to build it, you can use the following Docker command and procedurel: git clone https://github.com/codenotary/immudb.git docker run -it --rm -v $( ):/src golang:1.13-stretch sh -c docker run -it --rm -v $( ):/src golang:1.13-stretch sh -c # Linux pwd 'cd /src && GOOS=linux GOARCH=amd64 make immuclient-static' # Microsoft Windows pwd 'cd /src && GOOS=windows GOARCH=amd64 make immuclient-static' Now you’ll find the immuclient binary in the repository folder and ready to be used. gives you details how to use it. ./immuclient --help Add a record to immudb ./immuclient safeset mykey myvalue ./immuclient -a <immudb-ip> safeset mykey myvalue # same system where immudb server is running # immudb server runs on a remote system You'll receive something similar to: ./immuclient safeset k1 v1
index: 307
key: k1
value: v1 : 4a6a18172eba5a3ea49a3caf147ac405c874ed4c922cc7dafe0dce5ff85f35aa
time: 2020–05–13 04:01:30 -0400 EDT
verified: hash true Get the record from immudb ./immuclient safeget mykey ./immuclient mykey ./immuclient -a <immudb-ip> safeget mykey # same system where immudb server is running # get the value history history # immudb server runs on a remote system The and commands do a consistency check for the values as well. safeGet safeSet Now you could store any kind of data, like the content of a sensitive database field, public certificate or a even a configuration file. Let’s try with a local Dockerfile and make sure there are not new lines or special characters in our value. ./immuclient safeset Dockerfile1 $( -n | base64 -w 0) echo " " $(cat Dockerfile) To get the data back, you need to make sure to convert it again. As the output of safeget contains more than just the value, as seen here: ./immuclient safeget Dockerfile1
index:          309
key:            Dockerfile1
value:          RlJPTSBnb2xhbmc6MS4xMy1zdHJldGNoIGFzIGJ1aWxkCldPUktESVIgL3NyYwpDT1BZIC4gLgpSVU4gR09PUz1saW51eCBHT0FSQ0g9YW1kNjQgbWFrZSBpbW11YWRtaW4tc3RhdGljCkZST00gdWJ1bnR1OjE4LjA0Ck1BSU5UQUlORVIgdkNoYWluLCBJbmMuICA8aW5mb0B2Y2hhaW4udXM+CgpDT1BZIC0tZnJvbT1idWlsZCAvc3JjL2ltbXVhZG1pbiAvdXNyL2xvY2FsL2Jpbi9pbW11YWRtaW4KCkFSRyBJTU1VX1VJRD0iMzMyMiIKQVJHIElNTVVfR0lEPSIzMzIyIgoKRU5WIElNTVVBRE1JTl9JTU1VREItQUREUkVTUz0iMTI3LjAuMC4xIiBcCiAgICBJTU1VQURNSU5fSU1NVURCLVBPUlQ9IjMzMjIiIFwKICAgIElNTVVEQl9NVExTPSJmYWxzZSIgCgpSVU4gYWRkZ3JvdXAgLS1zeXN0ZW0gLS1naWQgJElNTVVfR0lEIGltbXUgJiYgXAogICAgYWRkdXNlciAtLXN5c3RlbSAtLXVpZCAkSU1NVV9VSUQgLS1uby1jcmVhdGUtaG9tZSAtLWluZ3JvdXAgaW1tdSBpbW11ICYmIFwKICAgIGNobW9kICt4IC91c3IvbG9jYWwvYmluL2ltbXVhZG1pbgoKVVNFUiBpbW11CkVOVFJZUE9JTlQgWyIvdXNyL2xvY2FsL2Jpbi9pbW11YWRtaW4iXQ== :           dfca217e2d87dccb8fd3fe8c1b49e620cc4ece8dc9c9fc2384cb6f6c9617eddb
time:           2020-05-13 05:19:19 -0400 EDT
verified: hash true the command is a bit more complex ./immuclient safeget Dockerfile1 | grep | cut -d -f2 | xargs -n | base64 -di "^value" ":" echo immudb SDKs There are many options for developers using the SDKs for Go Java, Node.js, Python These can be found in a developer jumpstart guide: https://docs.immudb.io/master/jumpstart.html#contents and the API descriptions: https://docs.immudb.io/master/sdks-api.html There is also a great Go SDK video tutorial: https://www.youtube.com/watch?v=qCC_AghFiw4 Check out immudb, the immutable database, written in Go: https://github.com/codenotary/immudb

Stories, News & Mentions about VODENO

Categories

Trending Topics

Stories, News & Mentions about VODENO

Vodeno’s Stories on HackerNoon

Categories

Trending Topics