prepare for a new release

oceanprotocol · Sep 16, 2020 · ff2cb2a · ff2cb2a
1 parent 0a99d93
commit ff2cb2a
Show file tree

Hide file tree

Showing 23 changed files with 26 additions and 27 deletions.
diff --git a/artifacts/BConst.json b/artifacts/BConst.json
@@ -2837,7 +2837,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.748Z",
+  "updatedAt": "2020-09-16T10:18:23.860Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/BFactory.json b/artifacts/BFactory.json
@@ -3311,7 +3311,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.755Z",
+  "updatedAt": "2020-09-16T10:18:23.863Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/BMath.json b/artifacts/BMath.json
@@ -16482,7 +16482,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.763Z",
+  "updatedAt": "2020-09-16T10:18:23.865Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/BNum.json b/artifacts/BNum.json
@@ -13037,7 +13037,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.774Z",
+  "updatedAt": "2020-09-16T10:18:23.871Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/BPool.json b/artifacts/BPool.json
@@ -66499,7 +66499,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.788Z",
+  "updatedAt": "2020-09-16T10:18:23.876Z",
   "devdoc": {
     "details": "Used by the (Ocean version) BFactory contract as a bytecode reference to     deploy new BPools. * This contract is is nearly identical to the BPool.sol contract at [1] The only difference is the \"Proxy contract functionality\" section  given below. We'd inherit from BPool if we could, for simplicity. But we can't, because the proxy section needs to access private variables declared in BPool, and Solidity disallows this. Therefore the best we can do for now is clearly demarcate the proxy section.  *  [1] https://github.com/balancer-labs/balancer-core/contracts/.",
     "methods": {},

diff --git a/artifacts/BToken.json b/artifacts/BToken.json
@@ -14000,7 +14000,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.834Z",
+  "updatedAt": "2020-09-16T10:18:23.901Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/BTokenBase.json b/artifacts/BTokenBase.json
@@ -13783,7 +13783,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.845Z",
+  "updatedAt": "2020-09-16T10:18:23.909Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/Context.json b/artifacts/Context.json
@@ -585,7 +585,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.870Z",
+  "updatedAt": "2020-09-16T10:18:23.932Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/DDO.json b/artifacts/DDO.json
@@ -4271,7 +4271,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.861Z",
+  "updatedAt": "2020-09-16T10:18:23.923Z",
   "devdoc": {
     "details": "DDO stands for Decentralized Document. It allows publishers     to publish their dataset metadata in decentralized way.     It follows the Ocean DID Document standard:      https://github.com/oceanprotocol/OEPs/blob/master/7/v0.2/README.md",
     "methods": {

diff --git a/artifacts/DTFactory.json b/artifacts/DTFactory.json
@@ -4665,7 +4665,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.731Z",
+  "updatedAt": "2020-09-16T10:18:23.857Z",
   "devdoc": {
     "author": "Ocean Protocol Team",
     "details": "Implementation of Ocean DataTokens Factory *      DTFactory deploys DataToken proxy contracts.     New DataToken proxy contracts are links to the template contract's bytecode.     Proxy contract functionality is based on Ocean Protocol custom implementation of ERC1167 standard.",

diff --git a/artifacts/DataTokenTemplate.json b/artifacts/DataTokenTemplate.json
@@ -14355,7 +14355,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.863Z",
+  "updatedAt": "2020-09-16T10:18:23.925Z",
   "devdoc": {
     "details": "DataTokenTemplate is an ERC20 compliant token template     Used by the factory contract as a bytecode reference to      deploy new DataTokens.",
     "methods": {

diff --git a/artifacts/Deployer.json b/artifacts/Deployer.json
@@ -783,7 +783,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.870Z",
+  "updatedAt": "2020-09-16T10:18:23.932Z",
   "devdoc": {
     "author": "Ocean Protocol Team",
     "details": "Contract Deployer     This contract allowes factory contract      to deploy new contract instances using     the same library pattern in solidity.     the logic it self is deployed only once, but     executed in the context of the new storage      contract (new contract instance)",

diff --git a/artifacts/ERC20.json b/artifacts/ERC20.json
@@ -11318,7 +11318,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.873Z",
+  "updatedAt": "2020-09-16T10:18:23.935Z",
   "devdoc": {
     "details": "Implementation of the {IERC20} interface. * This implementation is agnostic to the way tokens are created. This means that a supply mechanism has to be added in a derived contract using {_mint}. For a generic mechanism see {ERC20Mintable}. * TIP: For a detailed writeup see our guide https://forum.zeppelin.solutions/t/how-to-implement-erc20-supply-mechanisms/226[How to implement supply mechanisms]. * We have followed general OpenZeppelin guidelines: functions revert instead of returning `false` on failure. This behavior is nonetheless conventional and does not conflict with the expectations of ERC20 applications. * Additionally, an {Approval} event is emitted on calls to {transferFrom}. This allows applications to reconstruct the allowance for all accounts just by listening to said events. Other implementations of the EIP may not emit these events, as it isn't required by the specification. * Finally, the non-standard {decreaseAllowance} and {increaseAllowance} functions have been added to mitigate the well-known issues around setting allowances. See {IERC20-approve}.",
     "methods": {

diff --git a/artifacts/ERC20Pausable.json b/artifacts/ERC20Pausable.json
@@ -3236,7 +3236,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.868Z",
+  "updatedAt": "2020-09-16T10:18:23.930Z",
   "devdoc": {
     "details": "ERC20Pausable adds the ability to pause ERC20 compliant template      used by the ERC20Template contract for pausing the contract.",
     "methods": {

diff --git a/artifacts/FixedRateExchange.json b/artifacts/FixedRateExchange.json
@@ -17422,7 +17422,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.852Z",
+  "updatedAt": "2020-09-16T10:18:23.916Z",
   "devdoc": {
     "details": "FixedRateExchange is a fixed rate exchange Contract     Marketplaces uses this contract to allow consumers      exchanging datatokens with ocean token using a fixed      exchange rate.",
     "methods": {

diff --git a/artifacts/IERC20.json b/artifacts/IERC20.json
@@ -1854,7 +1854,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.876Z",
+  "updatedAt": "2020-09-16T10:18:23.938Z",
   "devdoc": {
     "details": "Interface of the ERC20 standard as defined in the EIP. Does not include the optional functions; to access them see {ERC20Detailed}.",
     "methods": {

diff --git a/artifacts/IERC20Template.json b/artifacts/IERC20Template.json
@@ -2867,7 +2867,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.860Z",
+  "updatedAt": "2020-09-16T10:18:23.922Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/Migrations.json b/artifacts/Migrations.json
@@ -885,7 +885,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.742Z",
+  "updatedAt": "2020-09-16T10:18:23.859Z",
   "devdoc": {
     "methods": {}
   },

diff --git a/artifacts/OPFCommunityFeeCollector.json b/artifacts/OPFCommunityFeeCollector.json
@@ -3296,7 +3296,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.850Z",
+  "updatedAt": "2020-09-16T10:18:23.914Z",
   "devdoc": {
     "details": "Ocean Protocol Foundation Community Fee Collector contract     allows consumers to pay very small fee as part of the exchange of      data tokens with ocean token in order to support the community of       ocean protocol and provide a sustainble development.",
     "methods": {

diff --git a/artifacts/Ownable.json b/artifacts/Ownable.json
@@ -3059,7 +3059,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.872Z",
+  "updatedAt": "2020-09-16T10:18:23.934Z",
   "devdoc": {
     "details": "Contract module which provides a basic access control mechanism, where there is an account (an owner) that can be granted exclusive access to specific functions. * This module is used through inheritance. It will make available the modifier `onlyOwner`, which can be applied to your functions to restrict their use to the owner.",
     "methods": {

diff --git a/artifacts/SafeMath.json b/artifacts/SafeMath.json
@@ -4882,7 +4882,7 @@
   },
   "networks": {},
   "schemaVersion": "3.2.0",
-  "updatedAt": "2020-09-16T09:22:58.871Z",
+  "updatedAt": "2020-09-16T10:18:23.933Z",
   "devdoc": {
     "details": "Wrappers over Solidity's arithmetic operations with added overflow checks. * Arithmetic operations in Solidity wrap on overflow. This can easily result in bugs, because programmers usually assume that an overflow raises an error, which is the standard behavior in high level programming languages. `SafeMath` restores this intuition by reverting the transaction when an operation overflows. * Using this library instead of the unchecked operations eliminates an entire class of bugs, so it's recommended to use it always.",
     "methods": {}

diff --git a/artifacts/address.json b/artifacts/address.json
diff --git a/docs/contracts/templates/DataTokenTemplate.md b/docs/contracts/templates/DataTokenTemplate.md
@@ -19,15 +19,15 @@ deploy new DataTokens.
 
 
 
-### `constructor(string name, string symbol, address minter, uint256 cap, string blob, address feeCollector)` (public)
+### `constructor(string name, string symbol, address minterAddress, uint256 cap, string blob, address feeCollector)` (public)
 
 
 
 constructor
 Called prior contract deployment
 
 
-### `initialize(string name, string symbol, address minter, uint256 cap, string blob, address feeCollector) → bool` (external)
+### `initialize(string name, string symbol, address minterAddress, uint256 cap, string blob, address feeCollector) → bool` (external)
 
 
 
@@ -45,7 +45,7 @@ Only the minter address can call it.
 msg.value should be higher than zero and gt or eq minting fee
 
 
-### `startOrder(address receiver, uint256 amount, bytes32 did, uint256 serviceId, address feeCollector, uint256 feePercentage)` (external)
+### `startOrder(uint256 amount, bytes32 did, uint256 serviceId, address mrktFeeCollector)` (external)
 
 
 
@@ -80,7 +80,7 @@ It unpauses the contract.
 Only called if the contract is paused.
 Only minter can call it.
 
-### `setMinter(address minter)` (external)
+### `setMinter(address minterAddress)` (external)
 
 
 
@@ -173,7 +173,7 @@ the total fee (including the community fee) needed for order.
 
 
 
-### `OrderStarted(uint256 amount, bytes32 did, uint256 serviceId, address receiver, uint256 startedAt, address feeCollector, uint256 marketFee)`
+### `OrderStarted(uint256 amount, bytes32 did, uint256 serviceId, uint256 startedAt, address mrktFeeCollector, uint256 marketFee)`