Coco network looks good. And finally Microsoft get in the ship. are you ready for moon?
Blockchain is going popular in every day every second.
Topic: Universal .NET framework for implementing BlockChain (Read 484 times)
I looked at the Coco framework.
A good solution, but requires a call to Azure.
Which is not always convenient, in particular because of the requirements of corporate secrecy.
We are implementing the BlockChain in the first place for private corporate networks.
A good solution, but requires a call to Azure.
Which is not always convenient, in particular because of the requirements of corporate secrecy.
We are implementing the BlockChain in the first place for private corporate networks.
Microsoft is gonna do that with its Coco framework.
Whenever there's a necessity for immutable data in enterprise environments you could just put it on a blockchain.
There will be some kind of a middleware to talk to it thru Coco.
It will be implemented into existing trusts inside the MS architecture, GPs and stuff will be aplicable.
Killer solution, being tested on Ethereum currently.
https://azure.microsoft.com/en-us/blog/announcing-microsoft-s-coco-framework-for-enterprise-blockchain-networks/
Whenever there's a necessity for immutable data in enterprise environments you could just put it on a blockchain.
There will be some kind of a middleware to talk to it thru Coco.
It will be implemented into existing trusts inside the MS architecture, GPs and stuff will be aplicable.
Killer solution, being tested on Ethereum currently.
https://azure.microsoft.com/en-us/blog/announcing-microsoft-s-coco-framework-for-enterprise-blockchain-networks/
The main feature of the .NET blockchain technology is the application universality.
It is planned to create a configurable framework for various applications.
For example:
1. Encryption of the source data can both be turned on and off.
2. The data can be left as it is in the original form or stored in its own format.
It is planned to create a configurable framework for various applications.
For example:
1. Encryption of the source data can both be turned on and off.
2. The data can be left as it is in the original form or stored in its own format.
What is the main feature of blockchain technology exactly on .NET framework?
The problem with relational databases is they are usually full of really private info, so there would have to be some strong measures in place to ensure it can leak the data or have security issues.
For this purpose it is planned to do Universal BlockChain .NET framework as configurable.
Administrators will be able to configure both levels of data protection and encryption.
Hello everyone!
Dmytro Kuiavets propose to discuss the idea of developing a universal .NET framework for implementing blockchain technologies for the corporate segment.
Typically large companies have their own systems already developed for specific platforms. Accordingly there is an entire intracorporate IT ecosystem. Source code of existing blockchain technologies is open and available but most of it is written in C, Python and Go.
For companies that built their IT-infrastructure with the .NET platform the advantage of open source code is reduced and the cost of implementing of technology is increasing.
In this case it must acquire new knowledge and edit the work of the whole infrastructure only in order to introduce blockchain into.
It turns out that companies need to acquire competence and develop mechanisms for integration of blockchain technologies with existing systems and/or products.
If you have a prepared .NET framework for deploying/connecting blockchain-services, this task becomes more realistic, less expensive and quickly solved. It also solves the issue of database configuration – .NET blockchain will be implemented in existing corporate databases, such as MS SQL and Oracle.
Dmytro Kuiavets propose to discuss the idea of developing a universal .NET framework for implementing blockchain technologies for the corporate segment.
Typically large companies have their own systems already developed for specific platforms. Accordingly there is an entire intracorporate IT ecosystem. Source code of existing blockchain technologies is open and available but most of it is written in C, Python and Go.
For companies that built their IT-infrastructure with the .NET platform the advantage of open source code is reduced and the cost of implementing of technology is increasing.
In this case it must acquire new knowledge and edit the work of the whole infrastructure only in order to introduce blockchain into.
It turns out that companies need to acquire competence and develop mechanisms for integration of blockchain technologies with existing systems and/or products.
If you have a prepared .NET framework for deploying/connecting blockchain-services, this task becomes more realistic, less expensive and quickly solved. It also solves the issue of database configuration – .NET blockchain will be implemented in existing corporate databases, such as MS SQL and Oracle.
Thanks Volodymyr, can you please lead this thread for future?
I do a lot of Microsoft SQL development and can see some potential there - it's easy to tweak values in a database without leaving a trace.. so with some audit trail triggers any change could be logged, hashed and put on a blockchain. And something like what SIA coin does for the backups, which is a distributed, encrypted backup..
The problem with relational databases is they are usually full of really private info, so there would have to be some strong measures in place to ensure it can leak the data or have security issues.
The problem with relational databases is they are usually full of really private info, so there would have to be some strong measures in place to ensure it can leak the data or have security issues.
I mean a timestamping/checksum mechanism for verifying that the data was correct at a point in time if it's stored in an existing relational database.
In addition, scanning a relational database for the presence of incorrect data.
And data recovery based on data from other server nodes.
In addition, scanning a relational database for the presence of incorrect data.
And data recovery based on data from other server nodes.
So you are referring to a relational blockchain database written in .NET? Or a timestamping/checksum mechanism for verifying that the data was correct at a point in time if it's stored in an existing relational database?
It is exactly Universal .NET framework for implementing BlockChain.
If I understand correctly, then Nicolas Dorier ported BlockChain to C# with reference to Bitcoin Core.
Accordingly, it does not solve the task of protecting existing relational data (like: MS SQL, ORACLE, ...) via BlockChain.
If I understand correctly, then Nicolas Dorier ported BlockChain to C# with reference to Bitcoin Core.
Accordingly, it does not solve the task of protecting existing relational data (like: MS SQL, ORACLE, ...) via BlockChain.
Isn't that the point of https://stratisplatform.com/ - Nicolas Dorier is involved, and he ported Bitcoin Core to C# as far as I'm aware.
Hello everyone!
Dmytro Kuiavets propose to discuss the idea of developing a universal .NET framework for implementing blockchain technologies for the corporate segment.
Typically large companies have their own systems already developed for specific platforms. Accordingly there is an entire intracorporate IT ecosystem. Source code of existing blockchain technologies is open and available but most of it is written in C, Python and Go.
For companies that built their IT-infrastructure with the .NET platform the advantage of open source code is reduced and the cost of implementing of technology is increasing.
In this case it must acquire new knowledge and edit the work of the whole infrastructure only in order to introduce blockchain into.
It turns out that companies need to acquire competence and develop mechanisms for integration of blockchain technologies with existing systems and/or products.
If you have a prepared .NET framework for deploying/connecting blockchain-services, this task becomes more realistic, less expensive and quickly solved. It also solves the issue of database configuration – .NET blockchain will be implemented in existing corporate databases, such as MS SQL and Oracle.
Dmytro Kuiavets propose to discuss the idea of developing a universal .NET framework for implementing blockchain technologies for the corporate segment.
Typically large companies have their own systems already developed for specific platforms. Accordingly there is an entire intracorporate IT ecosystem. Source code of existing blockchain technologies is open and available but most of it is written in C, Python and Go.
For companies that built their IT-infrastructure with the .NET platform the advantage of open source code is reduced and the cost of implementing of technology is increasing.
In this case it must acquire new knowledge and edit the work of the whole infrastructure only in order to introduce blockchain into.
It turns out that companies need to acquire competence and develop mechanisms for integration of blockchain technologies with existing systems and/or products.
If you have a prepared .NET framework for deploying/connecting blockchain-services, this task becomes more realistic, less expensive and quickly solved. It also solves the issue of database configuration – .NET blockchain will be implemented in existing corporate databases, such as MS SQL and Oracle.
Jump to: