Implementation of ERC1400 Smart Contract standard for Security Tokens (STO)
err plugin to interact with wikipedia.org
Renovate as a Github Action
err plugin to interact with meetup.com
err plugin to interact with whyd.com
Terraform Pull Request Automation
A collection of utilities for developing and running GitHub Actions
Write unit tests for Botkit.
startedrenovatebot/helm-charts
started time in 2 hours
startedAnalogJ/scrutiny
started time in 5 hours
push eventgbin/err-backend-discord
commit sha 9bcfaa0558ee92f987f405666ad1930cb7e8b763
Update discord.py from 1.4.1 to 1.5.0
push time in 16 hours
create barnchgbin/err-backend-discord
branch : pyup-update-discord.py-1.4.1-to-1.5.0
created branch time in 16 hours
push eventConsenSys/ERC1400
commit sha c15fde45fa6b60a1d07aa9c6e9aa391e2a62d10b
[Fix Typo] "optionnaly" in readme
commit sha b24caaf182a3eab40e46d57bf03b83ab4536e577
Merge pull request #40 from andreataglia/master [Fix Typo] "optionnaly" in readme
push time in a day
pull request commentConsenSys/ERC1400
[Fix Typo] "optionnaly" in readme
Thanks, LGTM :)
comment created time in a day
push eventConsenSys/ERC1400
commit sha 1195d96c525e5e6f979678d18483d779d05de528
Typo in Fund Issuer
commit sha 462baaf31572d0f239243c556f161e0e1d3b5119
Merge pull request #55 from victorwiebe/patch-1 Typo in Fund Issuer
push time in a day
PR closed ConsenSys/ERC1400
<!--- Provide a general summary of your changes in the Title above -->
Description
<!--- Describe your changes in detail -->
Motivation and Context
<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->
How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->
Screenshots (if appropriate):
Types of changes
<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
<!--- Go over all the following points, and put an x in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
pr closed time in a day
pull request commentConsenSys/ERC1400
test: it should ask me to sign the CLA
I have read the CLA Document and I hereby sign the CLA
comment created time in a day
PR opened ConsenSys/ERC1400
<!--- Provide a general summary of your changes in the Title above -->
Description
<!--- Describe your changes in detail -->
Motivation and Context
<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->
How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->
Screenshots (if appropriate):
Types of changes
<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
<!--- Go over all the following points, and put an x in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
pr created time in a day
PR closed ConsenSys/ERC1400
<!--- Provide a general summary of your changes in the Title above -->
Description
<!--- Describe your changes in detail -->
Motivation and Context
<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->
How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->
Screenshots (if appropriate):
Types of changes
<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
<!--- Go over all the following points, and put an x in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
pr closed time in a day
pull request commentConsenSys/ERC1400
test: it should ask be to sign the CLA
I have read the CLA Document and I hereby sign the CLA
comment created time in a day
pull request commentConsenSys/ERC1400
test: it should ask be to sign the CLA
recheckcla
comment created time in a day
PR closed ConsenSys/ERC1400
<!--- Provide a general summary of your changes in the Title above -->
Description
<!--- Describe your changes in detail -->
Motivation and Context
<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->
How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->
Screenshots (if appropriate):
Types of changes
<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
<!--- Go over all the following points, and put an x in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
pr closed time in a day
pull request commentConsenSys/ERC1400
test: it should ask be to sign the CLA
I have read the CLA Document and I hereby sign the CLA
comment created time in a day
PR opened ConsenSys/ERC1400
<!--- Provide a general summary of your changes in the Title above -->
Description
<!--- Describe your changes in detail -->
Motivation and Context
<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->
How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->
Screenshots (if appropriate):
Types of changes
<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
<!--- Go over all the following points, and put an x in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
pr created time in a day
push eventConsenSys/ERC1400
commit sha f03d4e5ee172335479801f437856ef28026c8ca4
chore: add CLA
commit sha fdc6a2536f3e8e05e385e2ceb338116e352881c4
chore: add contribution templates
commit sha 666429b0923f37a8a378149ba79084484158ff10
chore: add stale configuration
commit sha 5dc229e4f17359078cf599e6ad5703c2f8adcd84
chore: add actual CLA
commit sha 812d84806b9a5d43b00e728041aa1fd1196f8235
Merge pull request #75 from ConsenSys/chore/cla Add CLA
push time in a day
push eventConsenSys/ERC1400
commit sha 5dc229e4f17359078cf599e6ad5703c2f8adcd84
chore: add actual CLA
push time in a day
startedGoogleContainerTools/kaniko
started time in a day
push eventConsenSys/ERC1400
commit sha 666429b0923f37a8a378149ba79084484158ff10
chore: add stale configuration
push time in a day
push eventConsenSys/ERC1400
commit sha dc410ebc3760c37b44aedf8710caa7f842d99422
chore: add stale configuration
push time in a day
issue closedConsenSys/ERC1400
Error in deployment while deploying to remix
We are using the same parameters as in truffle migration file, but still getting the error on remix.
closed time in a day
viraj124
issue commentConsenSys/ERC1400
Error in deployment while deploying to remix
Closing in favor of #35
comment created time in a day
push eventConsenSys/ERC1400
commit sha fdc6a2536f3e8e05e385e2ceb338116e352881c4
chore: add contribution templates
push time in a day
issue closedConsenSys/ERC1400
About Implimenting Partitions in ConsenSys's ERC1400
I read all smart contracts file in this ERC1400 example And the slides(Slide deck presenting ERC1400 features:) provided in ConsenSys.
The slide explains that partitions represent Asset state and Asset class in hex. But in ERC1400 Example partitions has only 3 state. And I have not understood how to write partitions representing different assets state and class in hex in details.
Has anyone concrete example codes?
closed time in a day
hamadayukinori
issue closedConsenSys/ERC1400
npm install on windows fails (solcpiler)
Windows users cant just npm i because of solcpiler.
> [email protected] prepack C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-a30f7271
> npm run test
> [email protected] test C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-a30f7271
> npm run build && mocha --harmony
> [email protected] build C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-a30f7271
> npm run clean && npm run build:sol
> [email protected] clean C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-a30f7271
> rm -rf build artifacts
> [email protected] build:sol C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-a30f7271
> solcpiler -i './contracts/*.sol' --solc-version="v0.4.24+commit.e67f0147" --output-artifacts-dir artifacts --insert-file-names imports
'solcpiler' is not recognized as an internal or external command,
Maybe cleraify to use Yarn :)
closed time in a day
RobertoSnap
issue closedConsenSys/ERC1400
Hi there! Hope you guys are doing well.
I am writing to you about multiple token issuance. I have been playing with that. I wrote a little module which calls issueByPartition multiple times. Obviously this is necessary because I am not going to call 100 times issueByPartition, I want to call 1 transaction call to issue for 100 investors.
function issueByPartitionMultiple(bytes32[] calldata partitions,
address[] calldata tokenHolders,
uint256[] calldata values,
bytes calldata data)
external
withControllerPermission //checks controller permission on contract, modifier works on other calls.
{
require(partitions.length == tokenHolders.length, "Check array lengths");
require(partitions.length == values.length, "Check array lengths");
for (uint i=0; i < partitions.length; i++) {
IERC1400(address(securityToken))
.issueByPartition(partitions[i], tokenHolders[i], values[i], data);
}
}
How have you guys solved this issue?
closed time in a day
victorwiebe
issue closedConsenSys/ERC1400
How data conservation is handled during the migrations ?
The ERC1400 seems to hold all the data of the implementation. Its migration code seems to only update the reference in the ERC1820 contract.
I wonder how data migration is handled? Is it not? Or is there a mecanism to access the data of the base contract from the new one ? And why not have a storage contract to handle this?
closed time in a day
ArvsIndrarys
issue closedConsenSys/ERC1400
yarn install fails when using node version > 10
I tried node 12.x, 13.x on windows and mac, build fails for all those combinations at node-gyp rebuild
node version 10.x works fine (it worked for me with 10.18.0 on windows)
Please add this to the readme, could save time for someone.
closed time in a day
manosamy
issue commentConsenSys/ERC1400
yarn install fails when using node version > 10
Closing this as the recommended version is now node 12.
comment created time in a day
pull request commentDjiit/cla-test
I have read the CLA Document and I hereby sign the CLA
comment created time in a day
push eventConsenSys/ERC1400
commit sha ca05509be1c3f14ea44ea6cccd0de961aba22b95
fix: working husky+lint-staged config
commit sha 814fb5cd57cef004b795d4e23d1e96ecf1a6def5
fix: do not lint:sol for now
commit sha b6fcea74a840004ad33724f3da0fc482b1435670
Merge pull request #70 from ConsenSys/fix/husky Fix Husky/linters usage
push time in a day
push eventwikiwarsgg/webapp
commit sha 914de6072ec2a663056f5b35a03d0b0adbc85bd1
⬆️ Update dependency @types/node to v13.13.21
push time in 2 days
PR merged wikiwarsgg/webapp
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| @types/node | devDependencies | patch | 13.13.15 -> 13.13.21 |
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr closed time in 2 days
push eventwikiwarsgg/soundboard
commit sha ce2f698056897103e65ef69d63ec669d414f4458
⬆️ Update dependency @types/node to v13.13.21
push time in 2 days
PR merged wikiwarsgg/soundboard
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| @types/node | devDependencies | patch | 13.13.15 -> 13.13.21 |
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr closed time in 2 days
push eventDjiit/dotfiles
commit sha ee80640fbe73dc2b3d33e38daf357714bafc30b4
feat: more brew tools
commit sha a4f30da43b6ddf00b38f9056be050e3d32658ef8
feat: add espanso config
push time in 4 days
push eventConsenSys/ERC1400
commit sha 814fb5cd57cef004b795d4e23d1e96ecf1a6def5
fix: do not lint:sol for now
push time in 5 days
push eventConsenSys/ERC1400
commit sha ca05509be1c3f14ea44ea6cccd0de961aba22b95
fix: working husky+lint-staged config
push time in 5 days
push eventConsenSys/ERC1400
commit sha e418e8068333996c215652084e3173d5b1307b04
chore: use github actions
commit sha 2c05f0c4007c5655880b55ff7f62e01943cb6e60
chore: cleanup scripts, ignore tests artifacts
commit sha 36ab45bff5b5bb473bffcac4b83ec40311538a15
chore: use github actions with node 12
commit sha 92501e102aa5555a49ce232697795025e04e9581
Merge pull request #68 from Djiit/feat/ci Use github actions
push time in 5 days
PR merged ConsenSys/ERC1400
The repo already define a yarn coverage script. I'm reusing it to bootstrap a simple CI scenario.
pr closed time in 5 days
push eventDjiit/ERC1400
commit sha 36ab45bff5b5bb473bffcac4b83ec40311538a15
chore: use github actions with node 12
push time in 5 days
push eventDjiit/ERC1400
commit sha 2c05f0c4007c5655880b55ff7f62e01943cb6e60
chore: cleanup scripts, ignore tests artifacts
push time in 5 days
PR opened ConsenSys/ERC1400
The repo already define a yarn coverage script. I'm reusing it to bootstrap a simple CI scenario.
pr created time in 5 days
push eventDjiit/ERC1400
commit sha db47c7e03b58dcd484f61576100effdf90eed35c
chore: use node 12
push time in 5 days
fork Djiit/ERC1400
Implementation of ERC1400 Smart Contract standard for Security Tokens (STO)
fork in 5 days
startedfrenck/awesome-home-assistant
started time in 7 days
startedserverless-nextjs/serverless-next.js
started time in 9 days
startedenv0/terratag
started time in 9 days
push eventwikiwarsgg/webapp
commit sha f69c32756b7ca32fb5cd39aec035f100858a8b62
⬆️ Update dependency @types/react to v16.9.49
commit sha 0bc024080a755cebc85ccb1ef6946b839cd8b7e7
⬆️ Update dependency twin.macro to v1.9.0
push time in 9 days
PR opened wikiwarsgg/webapp
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| lint-staged | devDependencies | minor | 10.2.11 -> 10.4.0 |
Release Notes
<details> <summary>okonet/lint-staged</summary>
v10.4.0
Features
v10.3.0
Features
v10.2.13
Bug Fixes
v10.2.12
Bug Fixes
- always use the default short diff format for submodules #902 (c7923ad)
- ensure supportsColor.level exists before stringifying it (aa9898e)
</details>
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr created time in 9 days
PR opened wikiwarsgg/webapp
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| husky | devDependencies | minor | 4.2.5 -> 4.3.0 |
Release Notes
<details> <summary>typicode/husky</summary>
v4.3.0
- Add
.cjsconfig file support #754
</details>
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr created time in 9 days
push eventwikiwarsgg/webapp
commit sha f69c32756b7ca32fb5cd39aec035f100858a8b62
⬆️ Update dependency @types/react to v16.9.49
commit sha ae3bbc7b769d0f4ccfa58d0e4107ce07d0c1ffd9
⬆️ Update dependency @types/node to v13.13.21
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 88ee0d7973b57fff17430e2a7d15ee4de975ddc8
⬆️ Update dependency @emotion/core to v10.0.35
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 1a913c507548978be73250715d655ff8a9eaa3fa
⬆️ Update dependency typescript to v4
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 88ee0d7973b57fff17430e2a7d15ee4de975ddc8
⬆️ Update dependency @emotion/core to v10.0.35
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha ec1a67d1580dc00c46215f1b87a2feabdd1c57ec
⬆️ Update dependency @commitlint/cli to v11
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 4817e671be9baa9ae5a8a84ba265eadd4c54e93c
⬆️ Update dependency twin.macro to v1.9.0
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 88ee0d7973b57fff17430e2a7d15ee4de975ddc8
⬆️ Update dependency @emotion/core to v10.0.35
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 6ddc55efcd1464615eb2ccfce69d0ab6996e2095
⬆️ Update dependency react-player to v2.6.2
push time in 9 days
PR opened wikiwarsgg/soundboard
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| lint-staged | devDependencies | minor | 10.2.11 -> 10.4.0 |
Release Notes
<details> <summary>okonet/lint-staged</summary>
v10.4.0
Features
v10.3.0
Features
v10.2.13
Bug Fixes
v10.2.12
Bug Fixes
- always use the default short diff format for submodules #902 (c7923ad)
- ensure supportsColor.level exists before stringifying it (aa9898e)
</details>
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr created time in 9 days
PR opened wikiwarsgg/soundboard
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| husky | devDependencies | minor | 4.2.5 -> 4.3.0 |
Release Notes
<details> <summary>typicode/husky</summary>
v4.3.0
- Add
.cjsconfig file support #754
</details>
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
pr created time in 9 days
push eventwikiwarsgg/soundboard
commit sha 75ec63e98c1e3757c5a64493b983934d406c847b
⬆️ Update dependency electron to v9.1.2
commit sha 88ee0d7973b57fff17430e2a7d15ee4de975ddc8
⬆️ Update dependency @emotion/core to v10.0.35
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 75e9b930255801f4a72ba1b68b705e1546927461
⬆️ Update dependency electron-builder to v22.8.1
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 4b85da733bb11df792426af6b568f4208955da21
⬆️ Update dependency electron to v9.3.1
push time in 9 days
push eventwikiwarsgg/soundboard
commit sha 342a2bee61db3bf66b44602081f7344959fc06b3
⬆️ Update dependency @types/react to v16.9.49
commit sha 10eaf8da54d1929f28be1c0497594178d20fa7b0
⬆️ Update dependency @types/node to v13.13.21
push time in 9 days
startedggreer/the_silver_searcher
started time in 11 days
startedmarnusw/date-fns-tz
started time in 14 days
startedFairwindsOps/polaris
started time in 15 days