| Category | Shards | Plasma | Side chain | |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"overrides": [ | |
{ | |
"files": "*.sol", | |
"options": { | |
"printWidth": 80, | |
"tabWidth": 4, | |
"useTabs": false, | |
"singleQuote": false, | |
"bracketSpacing": false |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some important details about Solidity specific/ Ethereum (Smart Contracts): | |
Background: | |
A contract has functionality (functions) and state (data). | |
Magic Global Variables: msg, tx, block | |
Anyone in the world has access to a smart contract (set/ get) the state. | |
But there are access restrictions that can be configured. | |
-address type is a 160 bit value, storing external contracts, keypairs. | |
-public generates a function that can be accessed outside of the contract. | |
-mapping(address => uint) public balances; complex datatype maps addresses to uint, like hashtables. *** use more advanced datatype |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Code is clean if it can be understood easily – by everyone on the team. | |
Clean code can be read and enhanced by a developer other than its original author. | |
With understandability comes readability, changeability, extensibility and maintainability. | |
_____________________________________ | |
## General rules | |
1. Follow standard conventions. | |
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible. | |
3. Boy scout rule. Leave the campground cleaner than you found it. | |
4. Always find root cause. Always look for the root cause of a problem. |
TOPIC | AWS | AZURE | FUNCTIONALITY |
---|---|---|---|
Compute | E |
| Topic | Centralized | Decentralized | Distributed Systems
| Topic | N Tier | Web-Queue-Worker | Microservices | Event-driven architecture
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On Neo4J Desktop browser console : | |
To connect to the graph | |
- Connect:play http://guides.neo4j.com/modeling_sandbox/05_refactoring_large_graphs.html | |
Steps: | |
- As our graph gets bigger in size it starts to become unfeasible to refactor the whole thing in one go. Instead we’ll have to update it in batches. | |
Manual batching | |
When batching we sacrifice the atomicity that we’d get if we did everything in one transaction. It’s therefore useful to make our refactoring queries idempotent in case we need to re-run them. We also need to decide which node we’re going to center the refactoring around. |
3 main areas to address
- Identification of the data controller & data processor
- Annonymizing the personal data
- Data subject can exercise certain data subject rights
- For e.g. Erase data at certain point of time
Data controller or processor - activities ( roles of various participants )
- Protocol developer (regular developer)
Use below command to convert certificate format
- Convert .CRT to .PEM format
- openssl x509 -inform der -in c:\Certificate\user2.crt (Your directory path) -out c:\Certificate\certificate_1.pem (Your directory path)
- Convert .CRT to .PFX format
- openssl pkcs12 -export -out c:\Certificate\certificate.pfx -inkey c:\Certificate\certificate_1.pem -in c:\Certificate\user2.crt
- Convert .PEM to .DER format
- openssl x509 -outform der -in c:\Certificate\certificatename.pem -out c:\Certificate\certificatename.der
NewerOlder