One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
pragma solidity ^0.7.0; | |
/** | |
* @title Storage | |
* @dev Store & retrieve value in a variable | |
*/ | |
contract Storage { | |
uint256 number; |
0x66Dc00A4290163456dFC47DB565ac5cb92D54262 | |
0xDe85ec760543890c56Ff9703F2AF7B6afECb8a99 |
pragma solidity ^0.6.6; | |
import "@openzeppelin/contracts/token/ERC20/ERC20.sol"; | |
contract MyERC is ERC20 { | |
constructor( string memory _name, string memory _denomination, uint256 _initialSupply, address _owner) public | |
ERC20(_name,_denomination) { | |
_mint(_owner, _initialSupply); | |
} |
Encode IPFS |
contract_decimals,contract_name,contract_ticker_symbol,contract_address,logo_url,last_transferred_at,type,balance,balance_24h,quote_rate,quote_rate_24h,quote,quote_24h,nft_data,supports_erc_0,supports_erc | |
18,"KyDy.org","KyDy.org","0xc85e0474068dba5b49450c26879541ee6cc94554","https://logos.covalenthq.com/tokens/1/0xc85e0474068dba5b49450c26879541ee6cc94554.png","2021-11-17T11:57:18Z","cryptocurrency","300000000000000000000000","300000000000000000000000","0.76100236",,"228300.7",,,"erc20", | |
18,"SFAr.io","SFA","0x16b3dd2970ad3f19c6068c65777530830d33773e","https://logos.covalenthq.com/tokens/1/0x16b3dd2970ad3f19c6068c65777530830d33773e.png","2021-09-19T13:49:29Z","cryptocurrency","300000000000000000000000","300000000000000000000000","0.32623658",,"97870.98",,,"erc20", | |
18,"Ether","ETH","0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee","https://www.covalenthq.com/static/images/icons/display-icons/ethereum-eth-logo.png",,"cryptocurrency","2658850070905045369","709738805937064554","2675.1182","2651.1624","7112.7383","1881.6 |
Having done a number of data projects over the years, and having seen a number of them up on GitHub, I've come to see that there's a wide range in terms of how "readable" a project is. I'd like to share some practices that I have come to adopt in my projects, which I hope will bring some organization to your projects.
Disclaimer: I'm hoping nobody takes this to be "the definitive guide" to organizing a data project; rather, I hope you, the reader, find useful tips that you can adapt to your own projects.
Disclaimer 2: What I’m writing below is primarily geared towards Python language users. Some ideas may be transferable to other languages; others may not be so. Please feel free to remix whatever you see here!
Disclaimer 3: I found the Cookiecutter Data Science page after finishing this blog post. Many ideas overlap here, though some directories are irrelevant in my work -- which is to
info |
texto |