time curl "http://localhost:8000/api/v0.1/bounties/?network=mainnet&idx_status=open&order_by=-web3_created&offset=125&limit=75"

[{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit-Network.tech/191/2139","created_on":"2019-02-18T06:49:29.497658Z","modified_on":"2019-02-18T15:47:55.566832Z","title":"Implement Calendar instead of Blocks for MyBit Trust","web3_created":"2019-01-16T17:44:19Z","value_in_token":"14000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Improvement","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit-Network.tech/issues/191","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-16T17:44:19Z","activities":[],"keywords":"JavaScript, HTML, Solidity, CSS, Shell","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.651913Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nTo enhance the user experience of MyBit Trust (trust.mybit.io and https://trust.mybit.io/create-new) We want to replace the current method of distributing crypto-assets based on Block numbers with a calendar feature.\r\n\r\nCurrent Behaviour: Choose in how many blocks the crypto-asset should be distributed.\r\nDesired Behaviour: Choose a future time from a calendar pop-up (including date and time in UTC) and the block number to distribute is calculated on the back-end without the user knowing.\r\n\r\n## Requirements\r\n1. Implement a Calendar feature instead of inputting blocks\r\n2. Users must be able to manually input dates and times in the calendar as well as scroll through and click on days and times.\r\n3. All times must be in UTC\r\n4. Calculation of Block number to distribute should be done on the back-end.\r\n5. Anywhere on dApp that mentions Block # should be changed to date (such as on transaction and redeem page if applicable).\r\n\r\n## To Submit\r\n1. Comment on task with a staging URL to get approval for design and placement.\r\n2. Please submit a pull request with the final version once complete.\r\n\r\n## Additional information\r\nIf you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","network":"mainnet","org_name":"MyBitFoundation","pk":1748,"issue_description_text":"## Introduction\r\nTo enhance the user experience of MyBit Trust (trust.mybit.io and https://trust.mybit.io/create-new) We want to replace the current method of distributing crypto-assets based on Block numbers with a calendar feature.\r\n\r\nCurrent Behaviour: Choose in how many blocks the crypto-asset should be distributed.\r\nDesired Behaviour: Choose a future time from a calendar pop-up (including date and time in UTC) and the block number to distribute is calculated on the back-end without the user knowing.\r\n\r\n## Requirements\r\n1. Implement a Calendar feature instead of inputting blocks\r\n2. Users must be able to manually input dates and times in the calendar as well as scroll through and click on days and times.\r\n3. All times must be in UTC\r\n4. Calculation of Block number to distribute should be done on the back-end.\r\n5. Anywhere on dApp that mentions Block # should be changed to date (such as on transaction and redeem page if applicable).\r\n\r\n## To Submit\r\n1. Comment on task with a staging URL to get approval for design and placement.\r\n2. Please submit a pull request with the final version once complete.\r\n\r\n## Additional information\r\nIf you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":2139,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":191,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit-Network.tech","idx_status":"open","token_value_time_peg":"2019-02-18T15:47:55.647246Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1748&network=mainnet","increase":"/issue/increase?pk=1748&network=mainnet","accept":"/issue/accept?pk=1748&network=mainnet","cancel":"/issue/cancel?pk=1748&network=mainnet","payout":"/issue/payout?pk=1748&network=mainnet","contribute":"/issue/contribute?pk=1748&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1748&network=mainnet","social_contribution":"/issue/social_contribution?pk=1748&network=mainnet","invoice":"/issue/invoice?pk=1748&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/spacemeshos/go-spacemesh/364/2137","created_on":"2019-02-18T06:49:23.381726Z","modified_on":"2019-02-18T15:47:56.705978Z","title":"implement abstract message sending retry","web3_created":"2019-01-16T16:13:44Z","value_in_token":"500000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/spacemeshos/go-spacemesh/issues/364","github_comments":0,"bounty_owner_address":"0xb0512f306b6d8a759f0a6ae9be27272429d94ee4","bounty_owner_email":"aviveyal07@gmail.com","bounty_owner_github_username":"avive","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-16T16:13:44Z","activities":[],"keywords":"Go, Assembly, p2p, blockchain","current_bounty":true,"value_in_eth":"500000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"346.05","value_in_usdt":"346.05","status":"open","now":"2019-02-18T16:03:19.662835Z","avatar_url":"http://localhost:8000/dynamic/avatar/spacemeshos","value_true":"0.50","issue_description":"# Overview / Motivation\r\n\r\n`ConnectionPool` manages the open connection we have, we might `Dial` and get a new connection which will be closed later we'll have another connection with the same peer and we decide to keep his.\r\n\r\nthis causes one of the initiators to cancel his procedure because the connection is stale. we need to figure out the connection is stale as soon as possible and maybe abstract a retry that tries a new connection or tries to locate another existing connection before giving up on the procedure.\r\n\r\n# The Task\r\n\r\nImplement retries on sending messages which consider connections closing meanwhile and retrying.\r\n\r\nthis aims to solves that a protocol that requests sending a message will not get a timeout if the connection is closed because of connections conflict. ( we will seamlessly retry sending on the other connection)\r\n\r\n# Implementation Notes\r\nTODO: Add links to relevant resources, specs, related issues, etc...\r\n\r\nOne possible solution is to supply connections only from `ConnectionPool` and wrap them in a way that tries finding a new connection on a message failure (at least once for now) before returning an error. \r\n\r\n# Time Estimation\r\n1.5 days (12 hours)\r\n\r\n# Contribution Guidelines\r\nImportant: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby) \r\n\r\n1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task\r\n2. Fork branch `develop` to your own repo and work in your repo\r\n3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)\r\n4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature\r\n5. When ready for code review, submit a PR from your repo back to branch `develop`\r\n6. Attach relevant issue to PR\r\n","network":"mainnet","org_name":"spacemeshos","pk":1746,"issue_description_text":"# Overview / Motivation\r\n\r\n`ConnectionPool` manages the open connection we have, we might `Dial` and get a new connection which will be closed later we'll have another connection with the same peer and we decide to keep his.\r\n\r\nthis causes one of the initiators to cancel his procedure because the connection is stale. we need to figure out the connection is stale as soon as possible and maybe abstract a retry that tries a new connection or tries to locate another existing connection before giving up on the procedure.\r\n\r\n# The Task\r\n\r\nImplement retries on sending messages which consider connections closing meanwhile and retrying.\r\n\r\nthis aims to solves that a protocol that requests sending a message will not get a timeout if the connection is closed because of connections conflict. ( we will seamlessly retry sending on the other connection)\r\n\r\n# Implementation Notes\r\nTODO: Add links to relevant resources, specs, related issues, etc...\r\n\r\nOne possible solution is to supply connections only from `ConnectionPool` and wrap them in a way that tries finding a new connection on a message failure (at least once for now) before returning an error. \r\n\r\n# Time Estimation\r\n1.5 days (12 hours)\r\n\r\n# Contribution Guidelines\r\nImportant: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby) \r\n\r\n1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task\r\n2. Fork branch `develop` to your own repo and work in your repo\r\n3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)\r\n4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature\r\n5. When ready for code review, submit a PR from your repo back to branch `develop`\r\n6. Attach relevant issue to PR","standard_bounties_id":2137,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":364,"github_org_name":"spacemeshos","github_repo_name":"go-spacemesh","idx_status":"open","token_value_time_peg":"2019-02-18T15:47:56.739748Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1746&network=mainnet","increase":"/issue/increase?pk=1746&network=mainnet","accept":"/issue/accept?pk=1746&network=mainnet","cancel":"/issue/cancel?pk=1746&network=mainnet","payout":"/issue/payout?pk=1746&network=mainnet","contribute":"/issue/contribute?pk=1746&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1746&network=mainnet","social_contribution":"/issue/social_contribution?pk=1746&network=mainnet","invoice":"/issue/invoice?pk=1746&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"https://spacemesh.io/join/","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Spacemesh - https://spacemesh.io","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/spacemeshos/go-spacemesh/427/2134","created_on":"2019-02-18T06:49:14.522911Z","modified_on":"2019-02-18T15:47:57.575135Z","title":"Time config should move to timesync package","web3_created":"2019-01-16T16:10:48Z","value_in_token":"300000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/spacemeshos/go-spacemesh/issues/427","github_comments":0,"bounty_owner_address":"0xb0512f306b6d8a759f0a6ae9be27272429d94ee4","bounty_owner_email":"aviveyal07@gmail.com","bounty_owner_github_username":"avive","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-16T16:10:48Z","activities":[],"keywords":"Go, Assembly, Shell, Batchfile, Makefile, Dockerfile","current_bounty":true,"value_in_eth":"300000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"207.63","value_in_usdt":"207.63","status":"open","now":"2019-02-18T16:03:19.671947Z","avatar_url":"http://localhost:8000/dynamic/avatar/spacemeshos","value_true":"0.30","issue_description":"# Overview / Motivation\r\n\r\n`timesync` used to be a part of `p2p`. after #158 this is not the case but unfortunately we left the `TimeConfig` struct under the `P2P` config.\r\nThe time config shouldn't be part of the `p2p` config.\r\n\r\n# The Task\r\n\r\nMove the `TimeConfig` out of `p2p` to its own domain (`timesync`) and make sure it is loaded well.\r\nthe loading order is this where first is loaded first and last overrides.\r\n\r\n- Default\r\n- Config file\r\n- CLI Flags\r\n\r\n# Time Estimation\r\n6 hours\r\n\r\n# Implementation Notes\r\n\r\nwe put configs under a `config` package within the parent package. other places config loading code might be is `app/cmd/root.go` , `app/main` , `config`.\r\n\r\n# Contribution Guidelines\r\nImportant: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby)\r\n\r\n1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task\r\n2. Fork branch `develop` to your own repo and work in your repo\r\n3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)\r\n4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature\r\n5. When ready for code review, submit a PR from your repo back to branch `develop`\r\n6. Attach relevant issue to PR\r\n","network":"mainnet","org_name":"spacemeshos","pk":1743,"issue_description_text":"# Overview / Motivation\r\n\r\n`timesync` used to be a part of `p2p`. after #158 this is not the case but unfortunately we left the `TimeConfig` struct under the `P2P` config.\r\nThe time config shouldn't be part of the `p2p` config.\r\n\r\n# The Task\r\n\r\nMove the `TimeConfig` out of `p2p` to its own domain (`timesync`) and make sure it is loaded well.\r\nthe loading order is this where first is loaded first and last overrides.\r\n\r\n- Default\r\n- Config file\r\n- CLI Flags\r\n\r\n# Time Estimation\r\n6 hours\r\n\r\n# Implementation Notes\r\n\r\nwe put configs under a `config` package within the parent package. other places config loading code might be is `app/cmd/root.go` , `app/main` , `config`.\r\n\r\n# Contribution Guidelines\r\nImportant: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby)\r\n\r\n1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task\r\n2. Fork branch `develop` to your own repo and work in your repo\r\n3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)\r\n4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature\r\n5. When ready for code review, submit a PR from your repo back to branch `develop`\r\n6. Attach relevant issue to PR","standard_bounties_id":2134,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":427,"github_org_name":"spacemeshos","github_repo_name":"go-spacemesh","idx_status":"open","token_value_time_peg":"2019-02-18T15:47:57.595891Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1743&network=mainnet","increase":"/issue/increase?pk=1743&network=mainnet","accept":"/issue/accept?pk=1743&network=mainnet","cancel":"/issue/cancel?pk=1743&network=mainnet","payout":"/issue/payout?pk=1743&network=mainnet","contribute":"/issue/contribute?pk=1743&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1743&network=mainnet","social_contribution":"/issue/social_contribution?pk=1743&network=mainnet","invoice":"/issue/invoice?pk=1743&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"https://spacemesh.io/join/","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Spacemesh - https://spacemesh.io","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3544/2128","created_on":"2019-02-18T06:48:52.840807Z","modified_on":"2019-02-18T15:47:58.299236Z","title":"BUILD Reserve Bounties Improvements","web3_created":"2019-01-16T09:35:59Z","value_in_token":"450000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/gitcoinco/web/issues/3544","github_comments":0,"bounty_owner_address":"0x5df67bdf139abc95b0b3a5851875a73a5e722c0e","bounty_owner_email":"alisa.march@consensys.net","bounty_owner_github_username":"PixelantDesign","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-15T09:35:59Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:48:53.803337Z","profile":{"id":3,"handle":"pixelantdesign","github_url":"https://github.com/pixelantdesign","avatar_url":"http://localhost:8000/dynamic/avatar/pixelantdesign","url":"/profile/pixelantdesign"},"metadata":{"new_bounty":{"id":1737,"title":"BUILD Reserve Bounties Improvements","token_name":"ETH","value_in_eth":"450000000000000000","value_in_token":"450000000000000000","value_in_usdt_now":"311.45","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:48:53.131733+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1737,"tip":null}],"keywords":"JavaScript, HTML, Django","current_bounty":true,"value_in_eth":"450000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"311.45","value_in_usdt":"311.45","status":"open","now":"2019-02-18T16:03:19.682549Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"0.45","issue_description":"##### Description\r\n\r\nAs of now, a funder can come reserve a bounty for a user `X` while creating a bounty `/new`.\r\nThe created bounty is reserved for `X` for upto 72 hours during which only he can start work on it.\r\nAfter that -> the issue is no longer reserved and is open to everyone to work on.\r\n\r\nPR where it was built out: https://github.com/gitcoinco/web/pull/2950\r\n\r\n###### Issues \r\n\r\n- Right now, a reserved issue pops up into the `/explorer` for everyone even though they cannot start work on it.\r\n- We have a simple check to determine if a reserved issue is [open](https://github.com/gitcoinco/web/blob/master/app/assets/v2/js/pages/bounty_details.js#L431-L445) to the public, this means even after 72 hours expire -> we maintain who the issue was reserved for.\r\nIf the grant owner edits the issue details -> the checks kick in and the issue is reserved again (which should not happen )\r\n- There are instances where the funder may want the reserved issue to go beyond 72 hours (3 days)  and that doesn't happen at the moment.\r\n\r\n##### PR should Fix\r\n\r\n- Introduce input on the same row as reserved for in `/new` which asks \r\n `Release to the public after` X with drop down with options  `after 3 days, after a week, keep reserved` which map to corresponding hours \r\n- Introduce a new state -> reserved. \r\n- Any bounty created which is  reserved for a user -> would be in this newly created state\r\n- If the reserved bounty is started by user -> issue would transition to `Work Started`\r\n- If the bounty is no longer reserved (aka reserved time elapses) remove the reserved for User from db & transition issue to `Open State`\r\n- Add new state to the filter on the `explorer` to enable logged in user to see bounties reserved for them\r\n- ensure reserved bounty appears on `explorer` only to the users who have an active reservation\r\n- provide and button on the issue detail to force release the issue if needed. (Aka update dp to remove the reservedFor Data ) \r\n\r\nDiscussions : https://github.com/gitcoinco/web/issues/3502\r\n\r\n\r\n##### Note\r\n\r\nThis task would undergo PR reviews and feedback would have to be worked upon\r\n","network":"mainnet","org_name":"gitcoinco","pk":1737,"issue_description_text":"##### Description\r\n\r\nAs of now, a funder can come reserve a bounty for a user `X` while creating a bounty `/new`.\r\nThe created bounty is reserved for `X` for upto 72 hours during which only he can start work on it.\r\nAfter that -> the issue is no longer reserved and is open to everyone to work on.\r\n\r\nPR where it was built out: https://github.com/gitcoinco/web/pull/2950\r\n\r\n###### Issues \r\n\r\n- Right now, a reserved issue pops up into the `/explorer` for everyone even though they cannot start work on it.\r\n- We have a simple check to determine if a reserved issue is [open](https://github.com/gitcoinco/web/blob/master/app/assets/v2/js/pages/bounty_details.js#L431-L445) to the public, this means even after 72 hours expire -> we maintain who the issue was reserved for.\r\nIf the grant owner edits the issue details -> the checks kick in and the issue is reserved again (which should not happen )\r\n- There are instances where the funder may want the reserved issue to go beyond 72 hours (3 days)  and that doesn't happen at the moment.\r\n\r\n##### PR should Fix\r\n\r\n- Introduce input on the same row as reserved for in `/new` which asks \r\n `Release to the public after` X with drop down with options  `after 3 days, after a week, keep reserved` which map to corresponding hours \r\n- Introduce a new state -> reserved. \r\n- Any bounty created which is  reserved for a user -> would be in this newly created state\r\n- If the reserved bounty is started by user -> issue would transition to `Work Started`\r\n- If the bounty is no longer reserved (aka reserved time elapses) remove the reserved for User from db & transition issue to `Open State`\r\n- Add new state to the filter on the `explorer` to enable logged in user to see bounties reserved for them\r\n- ensure reserved bounty appears on `explorer` only to the users who have an active reservation\r\n- provide and button on the issue detail to force release the issue if needed. (Aka update dp to remove the reservedFor Data ) \r\n\r\nDiscussions : https://github.com/gitcoinco/web/issues/3502\r\n\r\n\r\n##### Note\r\n\r\nThis task would undergo PR reviews and feedback would have to be worked upon","standard_bounties_id":2128,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3544,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:47:58.323985Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1737&network=mainnet","increase":"/issue/increase?pk=1737&network=mainnet","accept":"/issue/accept?pk=1737&network=mainnet","cancel":"/issue/cancel?pk=1737&network=mainnet","payout":"/issue/payout?pk=1737&network=mainnet","contribute":"/issue/contribute?pk=1737&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1737&network=mainnet","social_contribution":"/issue/social_contribution?pk=1737&network=mainnet","invoice":"/issue/invoice?pk=1737&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/crypto-meetup-dev/cryptomeetup-portal/232/2127","created_on":"2019-02-18T06:48:49.534797Z","modified_on":"2019-02-18T15:47:59.068626Z","title":"migrate tron.cryptomeetup.io to NEO with same rules","web3_created":"2019-01-16T03:47:50Z","value_in_token":"1500000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/crypto-meetup-dev/cryptomeetup-portal/issues/232","github_comments":0,"bounty_owner_address":"0x0a9d233c7a68d8679f9c0b42a412bd9d36edf63b","bounty_owner_email":"Anonymous","bounty_owner_github_username":"aDappDeveloper","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-04-16T03:47:50Z","activities":[],"keywords":"Vue, JavaScript, HTML, CSS","current_bounty":true,"value_in_eth":"1500000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"1038.16","value_in_usdt":"1038.16","status":"open","now":"2019-02-18T16:03:19.691506Z","avatar_url":"http://localhost:8000/dynamic/avatar/crypto-meetup-dev","value_true":"1.50","issue_description":"Cryptomeetup is a decentralized events platform powered by cutting-edge blockchain technology. Users can publish activities on the 3D virtual earth, and they can also buy and sell land assets to campaign for land administrators. We hope to combine blockchain games with activities to create a more sustainable developing game model.\r\n\r\nPlease Migrate cryptomeetup.io to NEO blockchain with same rules (You may check tron.cryptomeetup.io for reference):\r\n\r\nOn the 3D interface, provide 220 countries, which are unique NFT token.\r\n\r\nThe initial price of each country is 10 NEO. By transaction, the corresponding country's price will automatically rise. The price fluctuation will follow the rules below:\r\n\r\nlast transaction price | New Purchase price | Dividends for developers | Prize Pool\r\n<20 NEO                     | Price * 200 / 95        | 5%                                       | 2%\r\n20- 500 NEO              | Price* 135 / 96          | 4%                                      | 2%\r\n500-2000 NEO           | Price * 125 / 97         | 3%                                      | 2%\r\n2000-5000 NEO         | Price * 117 / 97          | 3%                                      | 2%\r\nlarger than 5000 NEO | Price * 115 / 98         | 2%                                      | 2%\r\n\r\nThe countdown timer of the prize pool is one month. For every 100 NEO used to buy a country token, the countdown will add 60 seconds. When the countdown reaches zero, the last purchaser of the game wins the prizes.\r\n\r\nWhen the countdown timer reaches zero , the next round will be opened automatically. At the beginning of each round, the owner of the country remains the owner of the country at the end of the previous round. However, the countdown timer and the starting price of the country will be reset.","network":"mainnet","org_name":"crypto-meetup-dev","pk":1736,"issue_description_text":"Cryptomeetup is a decentralized events platform powered by cutting-edge blockchain technology. Users can publish activities on the 3D virtual earth, and they can also buy and sell land assets to campaign for land administrators. We hope to combine blockchain games with activities to create a more sustainable developing game model.\r\n\r\nPlease Migrate cryptomeetup.io to NEO blockchain with same rules (You may check tron.cryptomeetup.io for reference):\r\n\r\nOn the 3D interface, provide 220 countries, which are unique NFT token.\r\n\r\nThe initial price of each country is 10 NEO. By transaction, the corresponding country's price will automatically rise. The price fluctuation will follow the rules below:\r\n\r\nlast transaction price | New Purchase price | Dividends for developers | Prize Pool\r\n<20 NEO                     | Price * 200 / 95        | 5%                                       | 2%\r\n20- 500 NEO              | Price* 135 / 96          | 4%                                      | 2%\r\n500-2000 NEO           | Price * 125 / 97         | 3%                                      | 2%\r\n2000-5000 NEO         | Price * 117 / 97          | 3%                                      | 2%\r\nlarger than 5000 NEO | Price * 115 / 98         | 2%                                      | 2%\r\n\r\nThe countdown timer of the prize pool is one month. For every 100 NEO used to buy a country token, the countdown will add 60 seconds. When the countdown reaches zero, the last purchaser of the game wins the prizes.\r\n\r\nWhen the countdown timer reaches zero , the next round will be opened automatically. At the beginning of each round, the owner of the country remains the owner of the country at the end of the previous round. However, the countdown timer and the starting price of the country will be reset.","standard_bounties_id":2127,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":232,"github_org_name":"crypto-meetup-dev","github_repo_name":"cryptomeetup-portal","idx_status":"open","token_value_time_peg":"2019-02-18T15:47:59.085490Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1736&network=mainnet","increase":"/issue/increase?pk=1736&network=mainnet","accept":"/issue/accept?pk=1736&network=mainnet","cancel":"/issue/cancel?pk=1736&network=mainnet","payout":"/issue/payout?pk=1736&network=mainnet","contribute":"/issue/contribute?pk=1736&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1736&network=mainnet","social_contribution":"/issue/social_contribution?pk=1736&network=mainnet","invoice":"/issue/invoice?pk=1736&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Cryptomeetup Dev Team     dev@cryptomeetup.io","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/Uniswap/uniswap-api/2/2125","created_on":"2019-02-18T06:48:42.634834Z","modified_on":"2019-02-18T15:48:00.050125Z","title":"Finish first version of Uniswap API","web3_created":"2019-01-15T16:09:24Z","value_in_token":"500000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/Uniswap/uniswap-api/issues/2","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-14T16:09:24Z","activities":[],"keywords":"Python, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"500.00","value_in_usdt":"500.00","status":"open","now":"2019-02-18T16:03:19.699744Z","avatar_url":"http://localhost:8000/dynamic/avatar/Uniswap","value_true":"500.00","issue_description":"This issue will be assigned to @conlan \r\n\r\nSpec: https://docs.google.com/document/d/1-FulegTvr_Mx6vdHbPXdYHg8K4g5zLlYDNFa_ILXQ5Y/edit?usp=sharing\r\n\r\n- [ ] GET /api/v1/directory\r\n- [x] GET /api/v1/exchange\r\n- [X] GET /api/v1/price\r\n- [X] GET /api/v1/ticker\r\n- [X] GET /api/v1/history\r\n- [ ] Document API\r\n- [x] Add to uniswap.info\r\n","network":"mainnet","org_name":"Uniswap","pk":1734,"issue_description_text":"This issue will be assigned to @conlan \r\n\r\nSpec: https://docs.google.com/document/d/1-FulegTvr_Mx6vdHbPXdYHg8K4g5zLlYDNFa_ILXQ5Y/edit?usp=sharing\r\n\r\n- [ ] GET /api/v1/directory\r\n- [x] GET /api/v1/exchange\r\n- [X] GET /api/v1/price\r\n- [X] GET /api/v1/ticker\r\n- [X] GET /api/v1/history\r\n- [ ] Document API\r\n- [x] Add to uniswap.info","standard_bounties_id":2125,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":2,"github_org_name":"Uniswap","github_repo_name":"uniswap-api","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:00.070361Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1734&network=mainnet","increase":"/issue/increase?pk=1734&network=mainnet","accept":"/issue/accept?pk=1734&network=mainnet","cancel":"/issue/cancel?pk=1734&network=mainnet","payout":"/issue/payout?pk=1734&network=mainnet","contribute":"/issue/contribute?pk=1734&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1734&network=mainnet","social_contribution":"/issue/social_contribution?pk=1734&network=mainnet","invoice":"/issue/invoice?pk=1734&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/w3f/Web3-collaboration/60/2123","created_on":"2019-02-18T06:48:37.997812Z","modified_on":"2019-02-18T15:48:01.089752Z","title":"Build simple Substrate runtime modules with a tutorial","web3_created":"2019-01-15T13:36:17Z","value_in_token":"900000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Other","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/w3f/Web3-collaboration/issues/60","github_comments":0,"bounty_owner_address":"0x158d0345a6458ee55a40badbb16502abfff10e4e","bounty_owner_email":"edward@web3.foundation","bounty_owner_github_username":"anaminguyen","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-07-14T13:36:17Z","activities":[],"keywords":"substrate, polkadot, web3, ui, tutorial","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"900.00","value_in_usdt":"900.00","status":"open","now":"2019-02-18T16:03:19.708315Z","avatar_url":"http://localhost:8000/dynamic/avatar/w3f","value_true":"900.00","issue_description":"We need more tutorials that help developers get acquainted to building for Polkadot. In this bounty we desire the creation of a tutorial that leads fellow community members through the necessary steps of creating a [Substrate](https://substrate.readme.io/) runtime module.\r\n\r\n\r\n**Example project 1**:\r\nCreate a simple module that hashes a piece of data and stores it on chain (please include a timestamp). The module must be also be able to check the hash and timestamp.\r\n\r\nThis task should include a simple UI plus a tutorial.\r\n\r\n**Example project 2**:\r\nTaking inspiration from [Gavin Wood’s talk at W3S](https://youtu.be/0IoUZdDi5Is?t=3261), we would like a tutorial that teaches the community how to build a [simple game that uses a Substrate runtime module](https://substrate.readme.io/docs/creating-a-custom-substrate-chain).\r\n\r\nThis task should include a simple UI (e.g. in a web browser) and include a tutorial.\r\n\r\n**Example project 3**:\r\nTake inspiration from the above example projects and come up with your own Substrate runtime modules.\r\n\r\nIt is likely that you will have to create a simple UI, plus you need to write an accompanying tutorial.\r\n\r\n### Requirements\r\nWhen undertaking the work for this bounty, be advised that a correct submission will:\r\n\r\n* Be open source. This work will be shared widely with the community.\r\n* Have a step-by-step tutorial that explains how to write the module. The tutorial will explain the reasoning as to why the module is designed as it is.\r\n* The module must function as requested and contain no compiler errors.\r\n\r\n### Bounty\r\n> **This issue now has a funding of 900.0 DAI (900.0 USD @ $1.0/DAI) attached to it as part of the Web 3 Foundation fund.**\r\n>\r\n\r\nJust as an FYI for all bounty hunters: the **total** pot of funds is 900 Dai, but we are looking for 3 submissions. That means that each *individual* submission is eligible for 300 Dai.\r\n\r\nKeep this in mind while applying! Thanks and good luck!\r\n\r\n","network":"mainnet","org_name":"w3f","pk":1733,"issue_description_text":"We need more tutorials that help developers get acquainted to building for Polkadot. In this bounty we desire the creation of a tutorial that leads fellow community members through the necessary steps of creating a [Substrate](https://substrate.readme.io/) runtime module.\r\n\r\n\r\n**Example project 1**:\r\nCreate a simple module that hashes a piece of data and stores it on chain (please include a timestamp). The module must be also be able to check the hash and timestamp.\r\n\r\nThis task should include a simple UI plus a tutorial.\r\n\r\n**Example project 2**:\r\nTaking inspiration from [Gavin Wood’s talk at W3S](https://youtu.be/0IoUZdDi5Is?t=3261), we would like a tutorial that teaches the community how to build a [simple game that uses a Substrate runtime module](https://substrate.readme.io/docs/creating-a-custom-substrate-chain).\r\n\r\nThis task should include a simple UI (e.g. in a web browser) and include a tutorial.\r\n\r\n**Example project 3**:\r\nTake inspiration from the above example projects and come up with your own Substrate runtime modules.\r\n\r\nIt is likely that you will have to create a simple UI, plus you need to write an accompanying tutorial.\r\n\r\n### Requirements\r\nWhen undertaking the work for this bounty, be advised that a correct submission will:\r\n\r\n* Be open source. This work will be shared widely with the community.\r\n* Have a step-by-step tutorial that explains how to write the module. The tutorial will explain the reasoning as to why the module is designed as it is.\r\n* The module must function as requested and contain no compiler errors.\r\n\r\n### Bounty\r\n> **This issue now has a funding of 900.0 DAI (900.0 USD @ $1.0/DAI) attached to it as part of the Web 3 Foundation fund.**\r\n>\r\n\r\nJust as an FYI for all bounty hunters: the **total** pot of funds is 900 Dai, but we are looking for 3 submissions. That means that each *individual* submission is eligible for 300 Dai.\r\n\r\nKeep this in mind while applying! Thanks and good luck!","standard_bounties_id":2123,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":60,"github_org_name":"w3f","github_repo_name":"Web3-collaboration","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:01.103496Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1733&network=mainnet","increase":"/issue/increase?pk=1733&network=mainnet","accept":"/issue/accept?pk=1733&network=mainnet","cancel":"/issue/cancel?pk=1733&network=mainnet","payout":"/issue/payout?pk=1733&network=mainnet","contribute":"/issue/contribute?pk=1733&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1733&network=mainnet","social_contribution":"/issue/social_contribution?pk=1733&network=mainnet","invoice":"/issue/invoice?pk=1733&network=mainnet"},"project_type":"cooperative","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Web 3 Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/trailofbits/manticore/1343/2121","created_on":"2019-02-18T06:48:28.926580Z","modified_on":"2019-02-18T15:48:02.325426Z","title":"Use enums instead of constants","web3_created":"2019-01-14T22:16:22Z","value_in_token":"100000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/trailofbits/manticore/issues/1343","github_comments":0,"bounty_owner_address":"0x4c6eb76d262cc6121843f74e1d18036adf03f1bf","bounty_owner_email":"vivek.m.singh93@gmail.com","bounty_owner_github_username":"vs77bb","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-14T22:16:22Z","activities":[],"keywords":"Python, Shell, Dockerfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"100.00","value_in_usdt":"100.00","status":"open","now":"2019-02-18T16:03:19.716621Z","avatar_url":"http://localhost:8000/dynamic/avatar/trailofbits","value_true":"100.00","issue_description":"There are many places where we use pure strings instead of enums and later we do comparisons on those strings which are rather slow.\r\n\r\nThis is probably not the most bottleneck here and there (I haven't profiled it), but it is still worth to change it for better.\r\n\r\nEthereum:\r\n* Gas setting: \r\n  * Tx type/sort {CREATE, CALL, DELEGATECALL}\r\n  * Tx result type {STOP, RETURN, SELFDESTRUCT, THROW, TXERROR, REVERT}\r\n\r\nNative: \r\n* Arch (i386, amd64, armv7) and arm64 in the future\r\n\r\nTODO steps:\r\n* [ ] Find out all cases like this and report it here to be confirmed\r\n* [ ] Fix each of the case individually - with its own PR, also please attach a small benchmark so we can see it helped for the better\r\n\r\nEDIT: The enums should also have some usability in mind - e.g. being able to render as a string.","network":"mainnet","org_name":"trailofbits","pk":1731,"issue_description_text":"There are many places where we use pure strings instead of enums and later we do comparisons on those strings which are rather slow.\r\n\r\nThis is probably not the most bottleneck here and there (I haven't profiled it), but it is still worth to change it for better.\r\n\r\nEthereum:\r\n* Gas setting: \r\n  * Tx type/sort {CREATE, CALL, DELEGATECALL}\r\n  * Tx result type {STOP, RETURN, SELFDESTRUCT, THROW, TXERROR, REVERT}\r\n\r\nNative: \r\n* Arch (i386, amd64, armv7) and arm64 in the future\r\n\r\nTODO steps:\r\n* [ ] Find out all cases like this and report it here to be confirmed\r\n* [ ] Fix each of the case individually - with its own PR, also please attach a small benchmark so we can see it helped for the better\r\n\r\nEDIT: The enums should also have some usability in mind - e.g. being able to render as a string.","standard_bounties_id":2121,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":1343,"github_org_name":"trailofbits","github_repo_name":"manticore","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:02.351924Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1731&network=mainnet","increase":"/issue/increase?pk=1731&network=mainnet","accept":"/issue/accept?pk=1731&network=mainnet","cancel":"/issue/cancel?pk=1731&network=mainnet","payout":"/issue/payout?pk=1731&network=mainnet","contribute":"/issue/contribute?pk=1731&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1731&network=mainnet","social_contribution":"/issue/social_contribution?pk=1731&network=mainnet","invoice":"/issue/invoice?pk=1731&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/oceanprotocol/ocean-bounties/14/2109","created_on":"2019-02-18T06:47:41.163961Z","modified_on":"2019-02-18T15:48:03.357019Z","title":"Ocean bounty : Create a marketplace on Ocean Protocol (cont.)","web3_created":"2019-01-11T16:22:37Z","value_in_token":"10000000000000000000000.00","token_name":"PROCN","token_address":"0xf2aabdd898a0139195b2b5da7387d43a45ded254","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/oceanprotocol/ocean-bounties/issues/14","github_comments":0,"bounty_owner_address":"0x5a8302aa7046eb0f8d2e9e6fd3dda3416d5ecd8b","bounty_owner_email":"Anonymous","bounty_owner_github_username":"chalidbdb","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-10T16:22:37Z","activities":[],"keywords":"marketplace, javascript, python, java, UX, frontend, oceanprotocol, squid","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.725010Z","avatar_url":"http://localhost:8000/dynamic/avatar/oceanprotocol","value_true":"0.00","issue_description":"# Ocean bounty : Create a front-end focused implementation of a marketplace on the Ocean Testnet\r\n## How can you help?\r\n\r\nWe invite you to create a marketplace on Ocean Protocol’s testnet! Here are [some tutorials](https://docs.oceanprotocol.com/tutorials/introduction/) to get you started. Through this bounty, we want to encourage developers to make use of our javascript library, Squid.js, and build on top of Ocean and come up with new and interesting front-end implementations of marketplaces.\r\n\r\n## How does a marketplace on Ocean Protocol function?\r\n\r\nA marketplace on the Ocean Protocol is a service where publishers can list the assets (data sets) available to them, which they consider have value, and consumers interested in this asset can see what’s available and purchase it. We have [different components](https://docs.oceanprotocol.com/concepts/components/) that make up the marketplace. You can get to know everything about how marketplaces on Ocean function by going through our [core concepts](https://docs.oceanprotocol.com/concepts/introduction/)\r\n\r\n## What type of marketplaces can you build?\r\nHere is a use case for a marketplace idea that can get you started on thinking about what to publish on a marketplace\r\n\r\n**Setup a Data Cleaning Service Marketplace-** You as a data scientist, would like to offer specialised expert data cleaning services to other organizations. You wish to obtain the data for cleaning and publish the cleaning data results using Ocean. You can consider setting up a marketplace to offer your services on. Other similar data scientists would also like to join your marketplace and offer similar services once the reputation of the marketplace is established.\r\n\r\nThese are just one such marketplace idea. Feel free to come up with similar ideas and use cases. You can bounce off your ideas with us on [Gitter](https://gitter.im/oceanprotocol/Lobby) before you start implementing them!\r\n\r\nSome of the domains that we would like to see interesting marketplace implementations include (but not limited to)\r\n- Artificial Intelligence \r\n- Healthcare \r\n- Big data/datascience  \r\n- Machine learning \r\n- Data commons (free data marketplace)\r\n- IOT\r\n- Autonomous vehicles\r\n\r\n**Some other ideas**\r\n- A *super* simple marketplace for buying & selling data at fixed price\r\n- A portal to publish/discover/consume commons data  \r\n- A data exchange that looks like a crypto token exchange (e.g. bittrex).\r\n- Integrate Ocean with an existing data science tool or IDE to buy & sell data, or publish/consume commons data\r\n- Integrate Ocean with an existing data marketplace to buy & sell data\r\n\r\n## How to start setting up a marketplace?\r\n\r\n Here are the materials that you need to get started\r\n- [OEPs for Ocean Protocol](https://github.com/oceanprotocol/OEPs) (will help understand the design and flow) \r\n- [Useful to understand how your marketplace can helps data scientists](https://blog.oceanprotocol.com/how-ocean-can-benefit-data-scientists-7e502e5f1a5f) (primary consumers) \r\n- [Setting up Ocean Protocol testnet](https://blog.oceanprotocol.com/a-dive-into-the-ocean-testnet-98fdb43456ce)\r\n- [Design of Ocean Protocol](https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa)\r\n- [PoC Marketplace](https://github.com/oceanprotocol/pleuston)\r\n- [Marketplace setup](https://docs.oceanprotocol.com/setup/marketplace/)\r\n- Step-by-Step [marketplace bootstraping from Scratch in React](https://docs.oceanprotocol.com/tutorials/react-setup/)\r\n- [Super helpful in general](https://docs.oceanprotocol.com/)\r\n- Advanced understanding of [on-chain access control on Ocean](https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c)\r\n\r\n## Before you start building\r\n\r\nBefore you start building, you should reach out to us through either a Github comment below or on our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) with\r\n\r\n1. What the use case of your marketplace would be?\r\n2. How you plan to approach the problem?\r\n3. A timeline of how long you think your solution will take to implement.\r\nThis will help us assist you in your project and ensure you are on the right path.\r\n\r\n## What would make us happy\r\nUse Squid.js to demonstrate a fresh approach to building the marketplaces with new user experiences. [Pleuston](https://github.com/oceanprotocol/pleuston) is our example of our demo marketplace. We want you to use our [Squid.js API](https://github.com/oceanprotocol/squid-js/tree/develop/src/examples). Here’s some of the [important APIs](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md).\r\n\r\nThis is a complete list of all the classes and corresponding methods. We want you to use as many of these methods as you can to come up with new front-end focussed implementations for marketplaces.\r\n\r\n**Please note** - The table format below may not appear properly on Gitcoin, please refer to the bounty on Github.\r\n\r\nClass | Method | Return Value | Javascript Implementation\r\n-- | -- | -- | --\r\nOcean | getInstance (js, java)/ Ocean (py) | Ocean | Implemented\r\nOcean | getAccounts | array[Account] | Implemented\r\nOcean | searchAssets | array[Asset] | Implemented\r\nOcean | searchAssetsByText | array[Asset] | Implemented\r\nOcean | searchOrders tbd | array[Order] | Not Implemented\r\nOcean | getOrdersByAccount | array[Order] | Implemented\r\nOcean | register | string | Implemented\r\nOcean | resolveDID | ddo | Under Implementation\r\nOcean | getOrder | Order | Under Implementation\r\nOcean | getAsset | Asset | Under Implementation\r\nAccount | getId | string | Implemented\r\nAccount | getOceanBalance | number/integer | Implemented\r\nAccount | getEtherBalance | number/integer | Implemented\r\nAccount | getBalance | Balance | Implemented\r\nAccount | requestTokens | number/integer | Implemented\r\nAsset | getId | string | Implemented\r\nAsset | purchase | Order | Implemented\r\nAsset | getDID | string | Under Implementation\r\nAsset | getDDO | ddo | Under Implementation\r\nAsset | publishMetadata | string | Under Implementation\r\nAsset | getMetadata | Metadata | Under Implementation\r\nAsset | updateMetadata | boolean | Under Implementation\r\nAsset | retireMetadata | boolean | Under Implementation\r\nAsset | getServiceAgreements | array[ServiceAgreement] | Under Implementation\r\nServiceAgreement | getId | string | Under Implementation\r\nServiceAgreement | getPrice | number/integer | Under Implementation\r\nServiceAgreement | getStatus | xxx | Under Implementation\r\nServiceAgreement | publish | xxx | Under Implementation\r\nServiceAgreement | retire | xxx | Under Implementation\r\nServiceAgreement | getAccess | xxx | Under Implementation\r\nOrder | getId | string | Implemented\r\nOrder | getStatus | AccessStatus | Implemented\r\nOrder | verifyPayment | boolean | Under Implementation\r\nOrder | pay | string | Implemented\r\nOrder | commit | boolean | Implemented\r\nOrder | consume | blob | Implemented\r\n\r\nWe want you to use these existing methods to create unique front end implementations of the marketplace. \r\nIncase you have any questions, we are always available on Gitter.\r\n\r\n## Seen this problem before?\r\n\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n\r\n## Questions & Reviews\r\n\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n\r\n## Things to know\r\n\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\nLastly, even if it is a contest bounty, we will reward all valuable contributions and efforts. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! :smiley:\r\n\r\n## Reward\r\n\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (price of Ocean Token during pre-launch was valued at 0.20 EUR/token. However, once the Ocean token is available on public exchanges, the Ocean token price will likely be different). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.\r\n","network":"mainnet","org_name":"oceanprotocol","pk":1721,"issue_description_text":"# Ocean bounty : Create a front-end focused implementation of a marketplace on the Ocean Testnet\r\n## How can you help?\r\n\r\nWe invite you to create a marketplace on Ocean Protocol’s testnet! Here are [some tutorials](https://docs.oceanprotocol.com/tutorials/introduction/) to get you started. Through this bounty, we want to encourage developers to make use of our javascript library, Squid.js, and build on top of Ocean and come up with new and interesting front-end implementations of marketplaces.\r\n\r\n## How does a marketplace on Ocean Protocol function?\r\n\r\nA marketplace on the Ocean Protocol is a service where publishers can list the assets (data sets) available to them, which they consider have value, and consumers interested in this asset can see what’s available and purchase it. We have [different components](https://docs.oceanprotocol.com/concepts/components/) that make up the marketplace. You can get to know everything about how marketplaces on Ocean function by going through our [core concepts](https://docs.oceanprotocol.com/concepts/introduction/)\r\n\r\n## What type of marketplaces can you build?\r\nHere is a use case for a marketplace idea that can get you started on thinking about what to publish on a marketplace\r\n\r\n**Setup a Data Cleaning Service Marketplace-** You as a data scientist, would like to offer specialised expert data cleaning services to other organizations. You wish to obtain the data for cleaning and publish the cleaning data results using Ocean. You can consider setting up a marketplace to offer your services on. Other similar data scientists would also like to join your marketplace and offer similar services once the reputation of the marketplace is established.\r\n\r\nThese are just one such marketplace idea. Feel free to come up with similar ideas and use cases. You can bounce off your ideas with us on [Gitter](https://gitter.im/oceanprotocol/Lobby) before you start implementing them!\r\n\r\nSome of the domains that we would like to see interesting marketplace implementations include (but not limited to)\r\n- Artificial Intelligence \r\n- Healthcare \r\n- Big data/datascience  \r\n- Machine learning \r\n- Data commons (free data marketplace)\r\n- IOT\r\n- Autonomous vehicles\r\n\r\n**Some other ideas**\r\n- A *super* simple marketplace for buying & selling data at fixed price\r\n- A portal to publish/discover/consume commons data  \r\n- A data exchange that looks like a crypto token exchange (e.g. bittrex).\r\n- Integrate Ocean with an existing data science tool or IDE to buy & sell data, or publish/consume commons data\r\n- Integrate Ocean with an existing data marketplace to buy & sell data\r\n\r\n## How to start setting up a marketplace?\r\n\r\n Here are the materials that you need to get started\r\n- [OEPs for Ocean Protocol](https://github.com/oceanprotocol/OEPs) (will help understand the design and flow) \r\n- [Useful to understand how your marketplace can helps data scientists](https://blog.oceanprotocol.com/how-ocean-can-benefit-data-scientists-7e502e5f1a5f) (primary consumers) \r\n- [Setting up Ocean Protocol testnet](https://blog.oceanprotocol.com/a-dive-into-the-ocean-testnet-98fdb43456ce)\r\n- [Design of Ocean Protocol](https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa)\r\n- [PoC Marketplace](https://github.com/oceanprotocol/pleuston)\r\n- [Marketplace setup](https://docs.oceanprotocol.com/setup/marketplace/)\r\n- Step-by-Step [marketplace bootstraping from Scratch in React](https://docs.oceanprotocol.com/tutorials/react-setup/)\r\n- [Super helpful in general](https://docs.oceanprotocol.com/)\r\n- Advanced understanding of [on-chain access control on Ocean](https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c)\r\n\r\n## Before you start building\r\n\r\nBefore you start building, you should reach out to us through either a Github comment below or on our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) with\r\n\r\n1. What the use case of your marketplace would be?\r\n2. How you plan to approach the problem?\r\n3. A timeline of how long you think your solution will take to implement.\r\nThis will help us assist you in your project and ensure you are on the right path.\r\n\r\n## What would make us happy\r\nUse Squid.js to demonstrate a fresh approach to building the marketplaces with new user experiences. [Pleuston](https://github.com/oceanprotocol/pleuston) is our example of our demo marketplace. We want you to use our [Squid.js API](https://github.com/oceanprotocol/squid-js/tree/develop/src/examples). Here’s some of the [important APIs](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md).\r\n\r\nThis is a complete list of all the classes and corresponding methods. We want you to use as many of these methods as you can to come up with new front-end focussed implementations for marketplaces.\r\n\r\n**Please note** - The table format below may not appear properly on Gitcoin, please refer to the bounty on Github.\r\n\r\nClass | Method | Return Value | Javascript Implementation\r\n-- | -- | -- | --\r\nOcean | getInstance (js, java)/ Ocean (py) | Ocean | Implemented\r\nOcean | getAccounts | array[Account] | Implemented\r\nOcean | searchAssets | array[Asset] | Implemented\r\nOcean | searchAssetsByText | array[Asset] | Implemented\r\nOcean | searchOrders tbd | array[Order] | Not Implemented\r\nOcean | getOrdersByAccount | array[Order] | Implemented\r\nOcean | register | string | Implemented\r\nOcean | resolveDID | ddo | Under Implementation\r\nOcean | getOrder | Order | Under Implementation\r\nOcean | getAsset | Asset | Under Implementation\r\nAccount | getId | string | Implemented\r\nAccount | getOceanBalance | number/integer | Implemented\r\nAccount | getEtherBalance | number/integer | Implemented\r\nAccount | getBalance | Balance | Implemented\r\nAccount | requestTokens | number/integer | Implemented\r\nAsset | getId | string | Implemented\r\nAsset | purchase | Order | Implemented\r\nAsset | getDID | string | Under Implementation\r\nAsset | getDDO | ddo | Under Implementation\r\nAsset | publishMetadata | string | Under Implementation\r\nAsset | getMetadata | Metadata | Under Implementation\r\nAsset | updateMetadata | boolean | Under Implementation\r\nAsset | retireMetadata | boolean | Under Implementation\r\nAsset | getServiceAgreements | array[ServiceAgreement] | Under Implementation\r\nServiceAgreement | getId | string | Under Implementation\r\nServiceAgreement | getPrice | number/integer | Under Implementation\r\nServiceAgreement | getStatus | xxx | Under Implementation\r\nServiceAgreement | publish | xxx | Under Implementation\r\nServiceAgreement | retire | xxx | Under Implementation\r\nServiceAgreement | getAccess | xxx | Under Implementation\r\nOrder | getId | string | Implemented\r\nOrder | getStatus | AccessStatus | Implemented\r\nOrder | verifyPayment | boolean | Under Implementation\r\nOrder | pay | string | Implemented\r\nOrder | commit | boolean | Implemented\r\nOrder | consume | blob | Implemented\r\n\r\nWe want you to use these existing methods to create unique front end implementations of the marketplace. \r\nIncase you have any questions, we are always available on Gitter.\r\n\r\n## Seen this problem before?\r\n\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n\r\n## Questions & Reviews\r\n\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n\r\n## Things to know\r\n\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\nLastly, even if it is a contest bounty, we will reward all valuable contributions and efforts. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! :smiley:\r\n\r\n## Reward\r\n\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (price of Ocean Token during pre-launch was valued at 0.20 EUR/token. However, once the Ocean token is available on public exchanges, the Ocean token price will likely be different). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.","standard_bounties_id":2109,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":14,"github_org_name":"oceanprotocol","github_repo_name":"ocean-bounties","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:03.382534Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1721&network=mainnet","increase":"/issue/increase?pk=1721&network=mainnet","accept":"/issue/accept?pk=1721&network=mainnet","cancel":"/issue/cancel?pk=1721&network=mainnet","payout":"/issue/payout?pk=1721&network=mainnet","contribute":"/issue/contribute?pk=1721&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1721&network=mainnet","social_contribution":"/issue/social_contribution?pk=1721&network=mainnet","invoice":"/issue/invoice?pk=1721&network=mainnet"},"project_type":"contest","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ocean Protocol Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/trailofbits/manticore/1260/2108","created_on":"2019-02-18T06:47:38.295869Z","modified_on":"2019-02-18T15:48:04.496798Z","title":"Heuristic of the race condition detector does not give interesting result","web3_created":"2019-01-11T04:17:31Z","value_in_token":"200000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/trailofbits/manticore/issues/1260","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-10T04:17:31Z","activities":[],"keywords":"Python, Shell, Dockerfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"200.00","value_in_usdt":"200.00","status":"open","now":"2019-02-18T16:03:19.733870Z","avatar_url":"http://localhost:8000/dynamic/avatar/trailofbits","value_true":"200.00","issue_description":"### Manticore version\r\nhttps://github.com/trailofbits/manticore/tree/e4e0829b6c962a40356ce2d8d6ea3b5b9ad64965\r\n\r\n### Summary of the problem\r\nThe current heuristic of the [race condition detector](https://github.com/trailofbits/manticore/blob/e4e0829b6c962a40356ce2d8d6ea3b5b9ad64965/manticore/ethereum/detectors.py#L582) can be summarized as:\r\n- Does a function write to a state variable which is read by another function?\r\n\r\nThis pattern does not give any interesting results, as it matches too many code without bug.\r\n\r\nWe could follow something closer to what oyente and securify do, like:\r\n- Is the `msg.value` of an internal call independent of other transactions?\r\n\r\nI am not sure that oyente/securify strategies give pertinent results, it may also lead to several cases where it's not a bug, so we may want to refine the heuristic. \r\n\r\n### Step to reproduce the behavior\r\n```\r\ncontract ERC20{\r\n    mapping(address => mapping(address => uint)) allowance;\r\n\r\n    function approve(address to, uint val){\r\n        if(allowance[msg.sender][to] + val > allowance[msg.sender][to]){\r\n            allowance[msg.sender][to] += val;  \r\n        }\r\n    }\r\n\r\n    function transfer(address from, uint val){\r\n        if(allowance[from][msg.sender] >= val){\r\n            allowance[from][msg.sender] -= val;\r\n        }   \r\n    }\r\n}\r\n```\r\n\r\n\r\n### Expected behavior\r\nNo bug\r\n\r\n### Actual behavior\r\n```\r\n$  manticore test.sol --detect-race-condition\r\nPotential race condition (transaction order dependency):\r\nValue has been stored in storage slot/index 107947620283194693777147330934714592376293967296602958269006860500381273712713 in transaction that called approve(address,uint256) and is now used in transaction that calls transfer(address,uint256).\r\nAn attacker seeing a transaction to transfer(address,uint256) could create a transaction to approve(address,uint256) with high gas and win a race.\r\n```\r\n\r\n","network":"mainnet","org_name":"trailofbits","pk":1720,"issue_description_text":"### Manticore version\r\nhttps://github.com/trailofbits/manticore/tree/e4e0829b6c962a40356ce2d8d6ea3b5b9ad64965\r\n\r\n### Summary of the problem\r\nThe current heuristic of the [race condition detector](https://github.com/trailofbits/manticore/blob/e4e0829b6c962a40356ce2d8d6ea3b5b9ad64965/manticore/ethereum/detectors.py#L582) can be summarized as:\r\n- Does a function write to a state variable which is read by another function?\r\n\r\nThis pattern does not give any interesting results, as it matches too many code without bug.\r\n\r\nWe could follow something closer to what oyente and securify do, like:\r\n- Is the `msg.value` of an internal call independent of other transactions?\r\n\r\nI am not sure that oyente/securify strategies give pertinent results, it may also lead to several cases where it's not a bug, so we may want to refine the heuristic. \r\n\r\n### Step to reproduce the behavior\r\n```\r\ncontract ERC20{\r\n    mapping(address => mapping(address => uint)) allowance;\r\n\r\n    function approve(address to, uint val){\r\n        if(allowance[msg.sender][to] + val > allowance[msg.sender][to]){\r\n            allowance[msg.sender][to] += val;  \r\n        }\r\n    }\r\n\r\n    function transfer(address from, uint val){\r\n        if(allowance[from][msg.sender] >= val){\r\n            allowance[from][msg.sender] -= val;\r\n        }   \r\n    }\r\n}\r\n```\r\n\r\n\r\n### Expected behavior\r\nNo bug\r\n\r\n### Actual behavior\r\n```\r\n$  manticore test.sol --detect-race-condition\r\nPotential race condition (transaction order dependency):\r\nValue has been stored in storage slot/index 107947620283194693777147330934714592376293967296602958269006860500381273712713 in transaction that called approve(address,uint256) and is now used in transaction that calls transfer(address,uint256).\r\nAn attacker seeing a transaction to transfer(address,uint256) could create a transaction to approve(address,uint256) with high gas and win a race.\r\n```","standard_bounties_id":2108,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":1260,"github_org_name":"trailofbits","github_repo_name":"manticore","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:04.510229Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1720&network=mainnet","increase":"/issue/increase?pk=1720&network=mainnet","accept":"/issue/accept?pk=1720&network=mainnet","cancel":"/issue/cancel?pk=1720&network=mainnet","payout":"/issue/payout?pk=1720&network=mainnet","contribute":"/issue/contribute?pk=1720&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1720&network=mainnet","social_contribution":"/issue/social_contribution?pk=1720&network=mainnet","invoice":"/issue/invoice?pk=1720&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/HERCone/HIPR/5/2105","created_on":"2019-02-18T06:47:27.031781Z","modified_on":"2019-02-18T15:48:06.335955Z","title":"Web3 client should be compatible with major providers","web3_created":"2019-01-10T21:00:05Z","value_in_token":"100000000000000000000.00","token_name":"HERC","token_address":"0x6251583e7d997df3604bc73b9779196e94a090ce","bounty_type":"Improvement","project_length":"Hours","experience_level":"Advanced","github_url":"https://github.com/HERCone/HIPR/issues/5","github_comments":0,"bounty_owner_address":"0x96706eb471f875a9a41442f358d3b34ba02f868b","bounty_owner_email":"logan@herc.one","bounty_owner_github_username":"lrgeoemtry","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-24T21:00:05Z","activities":[],"keywords":"C#, JavaScript, HTML, CSS, ShaderLab","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.742616Z","avatar_url":"http://localhost:8000/dynamic/avatar/HERCone","value_true":"0.00","issue_description":"The web3 client we are using is currently compatible only with Metamask's injected web3 instance.\r\nWe need it to be compatible with major injected web3 providers (Trust, Coinbase, etc).\r\n\r\nA good starting point to check out is: https://github.com/HERCone/HIPR/blob/master/WebBuild/public/javascripts/web3-client-internal.js","network":"mainnet","org_name":"HERCone","pk":1717,"issue_description_text":"The web3 client we are using is currently compatible only with Metamask's injected web3 instance.\r\nWe need it to be compatible with major injected web3 providers (Trust, Coinbase, etc).\r\n\r\nA good starting point to check out is: https://github.com/HERCone/HIPR/blob/master/WebBuild/public/javascripts/web3-client-internal.js","standard_bounties_id":2105,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":5,"github_org_name":"HERCone","github_repo_name":"HIPR","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:06.364660Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1717&network=mainnet","increase":"/issue/increase?pk=1717&network=mainnet","accept":"/issue/accept?pk=1717&network=mainnet","cancel":"/issue/cancel?pk=1717&network=mainnet","payout":"/issue/payout?pk=1717&network=mainnet","contribute":"/issue/contribute?pk=1717&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1717&network=mainnet","social_contribution":"/issue/social_contribution?pk=1717&network=mainnet","invoice":"/issue/invoice?pk=1717&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Hercules SEZC","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/HERCone/HIPR/4/2104","created_on":"2019-02-18T06:47:23.964336Z","modified_on":"2019-02-18T15:48:07.846464Z","title":"Cross-provider getBalance API","web3_created":"2019-01-10T20:58:45Z","value_in_token":"100000000000000000000.00","token_name":"HERC","token_address":"0x6251583e7d997df3604bc73b9779196e94a090ce","bounty_type":"Improvement","project_length":"Hours","experience_level":"Advanced","github_url":"https://github.com/HERCone/HIPR/issues/4","github_comments":0,"bounty_owner_address":"0x96706eb471f875a9a41442f358d3b34ba02f868b","bounty_owner_email":"logan@herc.one","bounty_owner_github_username":"lrgeoemtry","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-24T20:58:45Z","activities":[],"keywords":"C#, JavaScript, HTML, CSS, ShaderLab","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.751374Z","avatar_url":"http://localhost:8000/dynamic/avatar/HERCone","value_true":"0.00","issue_description":"A cross-provider getBalance function is needed in order to implement future planned features.\r\nThe API should be aware of multiple possibly injected web3 instances from multiple providers (Metamask, Trust, etc) and use them properly.\r\n\r\nA good starting point is this file: https://github.com/HERCone/HIPR/blob/master/WebBuild/public/javascripts/web3-client-internal.js","network":"mainnet","org_name":"HERCone","pk":1716,"issue_description_text":"A cross-provider getBalance function is needed in order to implement future planned features.\r\nThe API should be aware of multiple possibly injected web3 instances from multiple providers (Metamask, Trust, etc) and use them properly.\r\n\r\nA good starting point is this file: https://github.com/HERCone/HIPR/blob/master/WebBuild/public/javascripts/web3-client-internal.js","standard_bounties_id":2104,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":4,"github_org_name":"HERCone","github_repo_name":"HIPR","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:07.863398Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1716&network=mainnet","increase":"/issue/increase?pk=1716&network=mainnet","accept":"/issue/accept?pk=1716&network=mainnet","cancel":"/issue/cancel?pk=1716&network=mainnet","payout":"/issue/payout?pk=1716&network=mainnet","contribute":"/issue/contribute?pk=1716&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1716&network=mainnet","social_contribution":"/issue/social_contribution?pk=1716&network=mainnet","invoice":"/issue/invoice?pk=1716&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"https://herc.one/careers","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Hercules SEZC","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/spadebuilders/community/30/2097","created_on":"2019-02-18T06:46:59.820523Z","modified_on":"2019-02-18T15:48:09.784897Z","title":"Write a payment provider plugin for pretix to accept ETH","web3_created":"2019-01-10T07:01:53Z","value_in_token":"250000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/spadebuilders/community/issues/30","github_comments":0,"bounty_owner_address":"0xa8c7372dc993d7510c9c45425807d463967cbb12","bounty_owner_email":"boris@bmannconsulting.com","bounty_owner_github_username":"bmann","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-10T07:01:53Z","activities":[],"keywords":"","current_bounty":true,"value_in_eth":"250000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"173.03","value_in_usdt":"173.03","status":"open","now":"2019-02-18T16:03:19.759327Z","avatar_url":"http://localhost:8000/dynamic/avatar/spadebuilders","value_true":"0.25","issue_description":"From [discussions at EthMagicians](https://ethereum-magicians.org/t/charging-for-tickets-participant-numbers-event-ticketing-for-council-of-paris-2019/2321) we're going to be using [pretix](https://pretix.eu/about/en/) to run registration for Council of Paris 2019.\r\n\r\nFor now, we're going to use the fully hosted version and use their manual payment system to instruct people to donate to the EthMagicians wallet --> https://donations.ethereum-magicians.org.\r\n\r\nFor future events, it would be great to run our own instance -- e.g. ```tickets.ethereumevents.global``` -- that has an ETH payment provider plugin installed. There will be a separate issue for doing the initial install and some maintenance.\r\n\r\npretix is written in Django and has good instructions on how to [write a payment provider](https://docs.pretix.eu/en/latest/development/api/payment.html). The [Bitpay payment provider plugin](https://github.com/pretix/pretix-bitpay) may prove helpful to refer to.\r\n\r\nThe initial scope will be:\r\n- support ETH\r\n- display a configured event wallet address\r\n- watch for an incoming payment linked to the order\r\n- communicate back the successful transaction to indicate that the order is paid\r\n\r\nAside from building the feature, the bounty builder will be responsible for\r\n- creating a Github repo\r\n- releasing the code under Apache 2.0\r\n\r\nFuture feature requests and additional bounties will be listed in the new repo for this payment provider plugin. Feel free to use this thread to brainstorm future features (e.g. DAI and arbitrary ERC20 token support, NFT \"tickets\", etc.).","network":"mainnet","org_name":"spadebuilders","pk":1709,"issue_description_text":"From [discussions at EthMagicians](https://ethereum-magicians.org/t/charging-for-tickets-participant-numbers-event-ticketing-for-council-of-paris-2019/2321) we're going to be using [pretix](https://pretix.eu/about/en/) to run registration for Council of Paris 2019.\r\n\r\nFor now, we're going to use the fully hosted version and use their manual payment system to instruct people to donate to the EthMagicians wallet --> https://donations.ethereum-magicians.org.\r\n\r\nFor future events, it would be great to run our own instance -- e.g. ```tickets.ethereumevents.global``` -- that has an ETH payment provider plugin installed. There will be a separate issue for doing the initial install and some maintenance.\r\n\r\npretix is written in Django and has good instructions on how to [write a payment provider](https://docs.pretix.eu/en/latest/development/api/payment.html). The [Bitpay payment provider plugin](https://github.com/pretix/pretix-bitpay) may prove helpful to refer to.\r\n\r\nThe initial scope will be:\r\n- support ETH\r\n- display a configured event wallet address\r\n- watch for an incoming payment linked to the order\r\n- communicate back the successful transaction to indicate that the order is paid\r\n\r\nAside from building the feature, the bounty builder will be responsible for\r\n- creating a Github repo\r\n- releasing the code under Apache 2.0\r\n\r\nFuture feature requests and additional bounties will be listed in the new repo for this payment provider plugin. Feel free to use this thread to brainstorm future features (e.g. DAI and arbitrary ERC20 token support, NFT \"tickets\", etc.).","standard_bounties_id":2097,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":30,"github_org_name":"spadebuilders","github_repo_name":"community","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:09.805705Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1709&network=mainnet","increase":"/issue/increase?pk=1709&network=mainnet","accept":"/issue/accept?pk=1709&network=mainnet","cancel":"/issue/cancel?pk=1709&network=mainnet","payout":"/issue/payout?pk=1709&network=mainnet","contribute":"/issue/contribute?pk=1709&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1709&network=mainnet","social_contribution":"/issue/social_contribution?pk=1709&network=mainnet","invoice":"/issue/invoice?pk=1709&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"EthMagicians","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ccxt/ccxt/4457/2093","created_on":"2019-02-18T06:46:45.460653Z","modified_on":"2019-02-18T15:48:10.617435Z","title":"New exchange CrossExchange","web3_created":"2019-01-09T21:44:33Z","value_in_token":"40000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"改善","project_length":"Unknown","experience_level":"初心者","github_url":"https://github.com/ccxt/ccxt/issues/4457","github_comments":0,"bounty_owner_address":"0xa1d1a316b9b7abb1d6db9bf404ad647d678015e3","bounty_owner_email":"kitano@bitlabo.net","bounty_owner_github_username":"hirokita10","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-16T21:44:33Z","activities":[],"keywords":"JavaScript, Python, PHP, Shell","current_bounty":true,"value_in_eth":"40000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"27.68","value_in_usdt":"27.68","status":"open","now":"2019-02-18T16:03:19.765641Z","avatar_url":"http://localhost:8000/dynamic/avatar/ccxt","value_true":"0.04","issue_description":" CrossExchange is another Japan and Korea exchange very stable  innovative. \r\nThey currently support Bitcoin, Ethereum and Litecoin.\r\n\r\nwebsite:\r\nhttp://bit.ly/2SMA0Zc\r\n\r\nAPI: \r\nhttps://support.crossexchange.io/hc/en-us/categories/360001030591\r\n\r\n\r\n\r\n\r\nBTC/USDT\r\nETH/USDT\r\nXRP/USDT\r\nLTC/USDT\r\nADA/USDT\r\nEOS/USDT\r\nDASH/USDT\r\n","network":"mainnet","org_name":"ccxt","pk":1706,"issue_description_text":"CrossExchange is another Japan and Korea exchange very stable  innovative. \r\nThey currently support Bitcoin, Ethereum and Litecoin.\r\n\r\nwebsite:\r\nhttp://bit.ly/2SMA0Zc\r\n\r\nAPI: \r\nhttps://support.crossexchange.io/hc/en-us/categories/360001030591\r\n\r\n\r\n\r\n\r\nBTC/USDT\r\nETH/USDT\r\nXRP/USDT\r\nLTC/USDT\r\nADA/USDT\r\nEOS/USDT\r\nDASH/USDT","standard_bounties_id":2093,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":4457,"github_org_name":"ccxt","github_repo_name":"ccxt","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:10.644928Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1706&network=mainnet","increase":"/issue/increase?pk=1706&network=mainnet","accept":"/issue/accept?pk=1706&network=mainnet","cancel":"/issue/cancel?pk=1706&network=mainnet","payout":"/issue/payout?pk=1706&network=mainnet","contribute":"/issue/contribute?pk=1706&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1706&network=mainnet","social_contribution":"/issue/social_contribution?pk=1706&network=mainnet","invoice":"/issue/invoice?pk=1706&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Bitlabo","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ccxt/ccxt/4457/2094","created_on":"2019-02-18T06:46:47.975396Z","modified_on":"2019-02-18T15:48:11.501062Z","title":"New exchange CrossExchange","web3_created":"2019-01-09T21:38:56Z","value_in_token":"5000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Unknown","experience_level":"Beginner","github_url":"https://github.com/ccxt/ccxt/issues/4457","github_comments":0,"bounty_owner_address":"0xa1d1a316b9b7abb1d6db9bf404ad647d678015e3","bounty_owner_email":"kitano@bitlabo.net","bounty_owner_github_username":"hirokita10","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-23T21:38:56Z","activities":[],"keywords":"JavaScript, Python, PHP, Shell","current_bounty":true,"value_in_eth":"5000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"6.92","value_in_usdt":"6.92","status":"open","now":"2019-02-18T16:03:19.773262Z","avatar_url":"http://localhost:8000/dynamic/avatar/ccxt","value_true":"0.01","issue_description":" CrossExchange is another Japan and Korea exchange very stable  innovative. \r\nThey currently support Bitcoin, Ethereum and Litecoin.\r\n\r\nwebsite:\r\nhttp://bit.ly/2SMA0Zc\r\n\r\nAPI: \r\nhttps://support.crossexchange.io/hc/en-us/categories/360001030591\r\n\r\n\r\n\r\n\r\nBTC/USDT\r\nETH/USDT\r\nXRP/USDT\r\nLTC/USDT\r\nADA/USDT\r\nEOS/USDT\r\nDASH/USDT\r\n","network":"mainnet","org_name":"ccxt","pk":1707,"issue_description_text":"CrossExchange is another Japan and Korea exchange very stable  innovative. \r\nThey currently support Bitcoin, Ethereum and Litecoin.\r\n\r\nwebsite:\r\nhttp://bit.ly/2SMA0Zc\r\n\r\nAPI: \r\nhttps://support.crossexchange.io/hc/en-us/categories/360001030591\r\n\r\n\r\n\r\n\r\nBTC/USDT\r\nETH/USDT\r\nXRP/USDT\r\nLTC/USDT\r\nADA/USDT\r\nEOS/USDT\r\nDASH/USDT","standard_bounties_id":2094,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":4457,"github_org_name":"ccxt","github_repo_name":"ccxt","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:11.523873Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1707&network=mainnet","increase":"/issue/increase?pk=1707&network=mainnet","accept":"/issue/accept?pk=1707&network=mainnet","cancel":"/issue/cancel?pk=1707&network=mainnet","payout":"/issue/payout?pk=1707&network=mainnet","contribute":"/issue/contribute?pk=1707&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1707&network=mainnet","social_contribution":"/issue/social_contribution?pk=1707&network=mainnet","invoice":"/issue/invoice?pk=1707&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Bitlabo inc.","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereumjs/rustbn.js/25/2091","created_on":"2019-02-18T06:46:40.185846Z","modified_on":"2019-02-18T15:48:12.552340Z","title":"CI should run cargo build","web3_created":"2019-01-09T18:19:07Z","value_in_token":"60000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereumjs/rustbn.js/issues/25","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-08T18:19:07Z","activities":[],"keywords":"HTML, JavaScript, Rust, Makefile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"60.00","value_in_usdt":"60.00","status":"open","now":"2019-02-18T16:03:19.778106Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereumjs","value_true":"60.00","issue_description":"It will need to have access to rust, cargo and emscripten in the CI.\r\n\r\nOne can use the circleci files from https://github.com/ewasm/ewasm-precompiles or https://github.com/ewasm/ewasm-rust-api\r\n\r\nThe CI should:\r\n- run rustfmt\r\n- run cargo build\r\n- and run emscripten build (aka the makefile)\r\n","network":"mainnet","org_name":"ethereumjs","pk":1704,"issue_description_text":"It will need to have access to rust, cargo and emscripten in the CI.\r\n\r\nOne can use the circleci files from https://github.com/ewasm/ewasm-precompiles or https://github.com/ewasm/ewasm-rust-api\r\n\r\nThe CI should:\r\n- run rustfmt\r\n- run cargo build\r\n- and run emscripten build (aka the makefile)","standard_bounties_id":2091,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":25,"github_org_name":"ethereumjs","github_repo_name":"rustbn.js","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:12.573227Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1704&network=mainnet","increase":"/issue/increase?pk=1704&network=mainnet","accept":"/issue/accept?pk=1704&network=mainnet","cancel":"/issue/cancel?pk=1704&network=mainnet","payout":"/issue/payout?pk=1704&network=mainnet","contribute":"/issue/contribute?pk=1704&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1704&network=mainnet","social_contribution":"/issue/social_contribution?pk=1704&network=mainnet","invoice":"/issue/invoice?pk=1704&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/code-for-cause/tech-conferences/21/2089","created_on":"2019-02-18T06:46:33.162722Z","modified_on":"2019-02-18T15:48:14.389067Z","title":"Add cli support and support for cloud firestore as well in the already implemented script.","web3_created":"2019-01-09T07:52:58Z","value_in_token":"1000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Days","experience_level":"Beginner","github_url":"https://github.com/code-for-cause/tech-conferences/issues/21","github_comments":0,"bounty_owner_address":"0x23bb837fe8661f401f5a3462b108a120b45ba6bd","bounty_owner_email":"vikasharry03@gmail.com","bounty_owner_github_username":"vikaskyadav","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-04-09T07:52:58Z","activities":[],"keywords":"Python, Scraping, Scrapy, Firebase, Firestore, CLI, Data Curation, Scripting, BeautifulSoup, Selenium","current_bounty":true,"value_in_eth":"1000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"0.00","value_in_usdt":"0.00","status":"open","now":"2019-02-18T16:03:19.786976Z","avatar_url":"http://localhost:8000/dynamic/avatar/code-for-cause","value_true":"0.00","issue_description":"# Description\r\n\r\nThis is an extension to #14 . We need to extend the script to have support for `cloud firestore` as well.\r\n\r\n# Current behavior\r\n\r\nThe script supports some urls and sends data to firebase.\r\n\r\n\r\n# Required behavior\r\n\r\nAdd option to send data to `firebase` or `cloud firestore` as per requirement.\r\n\r\nSupport `CLI` options for:\r\n\r\n-  target as firebase or firestore.\r\n\r\n- whether to write to json file or not.\r\n\r\n- Add support for one more source if possible (similar to the already implemented script) to scrape https://www.eventbrite.com/\r\n\r\nThis issue is exclusively for @chocolatebrown.","network":"mainnet","org_name":"code-for-cause","pk":1702,"issue_description_text":"# Description\r\n\r\nThis is an extension to #14 . We need to extend the script to have support for `cloud firestore` as well.\r\n\r\n# Current behavior\r\n\r\nThe script supports some urls and sends data to firebase.\r\n\r\n\r\n# Required behavior\r\n\r\nAdd option to send data to `firebase` or `cloud firestore` as per requirement.\r\n\r\nSupport `CLI` options for:\r\n\r\n-  target as firebase or firestore.\r\n\r\n- whether to write to json file or not.\r\n\r\n- Add support for one more source if possible (similar to the already implemented script) to scrape https://www.eventbrite.com/\r\n\r\nThis issue is exclusively for @chocolatebrown.","standard_bounties_id":2089,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":21,"github_org_name":"code-for-cause","github_repo_name":"tech-conferences","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:14.406939Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1702&network=mainnet","increase":"/issue/increase?pk=1702&network=mainnet","accept":"/issue/accept?pk=1702&network=mainnet","cancel":"/issue/cancel?pk=1702&network=mainnet","payout":"/issue/payout?pk=1702&network=mainnet","contribute":"/issue/contribute?pk=1702&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1702&network=mainnet","social_contribution":"/issue/social_contribution?pk=1702&network=mainnet","invoice":"/issue/invoice?pk=1702&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Code-For-Cause","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/matterinc/PeepethClient/11/2084","created_on":"2019-02-18T06:46:16.057513Z","modified_on":"2019-02-18T15:48:17.020986Z","title":"Feature: add image or video to peep ","web3_created":"2019-01-07T23:16:04Z","value_in_token":"100000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Weeks","experience_level":"Intermediate","github_url":"https://github.com/matterinc/PeepethClient/issues/11","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-06T23:16:04Z","activities":[],"keywords":"Swift, HTML, Ruby","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"100.00","value_in_usdt":"100.00","status":"open","now":"2019-02-18T16:03:19.795679Z","avatar_url":"http://localhost:8000/dynamic/avatar/matterinc","value_true":"100.00","issue_description":"**Current behavior:**\r\nNow you can only send Peep with some text data in it.\r\n\r\n**Expected behavior:**\r\nNeed to send Peep with image or video data in it both to PeepEth server and to blockchain. \r\n\r\n**Solution:**\r\nIt’s needed to prepare sending data to server and Ethereum blockchain.\r\nCarefully look at how Peeps are sending now.\r\nSending controller is _SendPeepViewController_.\r\nAfter tapping \"Send\" button and writing correct password will be formed Server Peep:\r\n```swift\r\nlet peep = Peep(type: \"peep\",\r\n                content: content,\r\n                pic: \"\",\r\n                untrustedAddress: address!,\r\n                untrustedTimestamp: Int(Date().timeIntervalSince1970),\r\n                shareID: shareHash,\r\n                parentID: parentHash)\r\n\r\nlet createdServerPeep = CreateServerPeep(ipfs: \"xxx\",\r\n                                         author: address!,\r\n                                         content: content,\r\n                                         parentID: parentHash,\r\n                                         shareID: shareHash,\r\n                                         twitterShare: false,\r\n                                         picIpfs: \"\", // LOOK, its empty now. But it most likely shouldn't be\r\n                                         origContents: peep,\r\n                                         shareNow: true)\r\n```\r\nThen peep is posting to Peepeth server. In response you will get peeps hash from IPFS. In case of success you can optionally post peep to blockchain. But most likely you will not need to change anything further, since only a hash of a peep is required to send a transaction.\r\n\r\nPerhaps you need just to load image to some server and use its link when forming Peeps data. To get more info send Peep from Desktop PeepEth in Chrome using Developer Tools to “reverse engineer it”.\r\n\r\n**Acceptance Criteria:**\r\nThe code is written in new branch named feature/sendMedia or something like that.\r\nThe code implements the targets described above.\r\nThe code can be merged into the develop branch without conflicts.\r\n\r\n**Required Skill:**\r\nParticipants needs to have experience in Swift software development.","network":"mainnet","org_name":"matterinc","pk":1698,"issue_description_text":"**Current behavior:**\r\nNow you can only send Peep with some text data in it.\r\n\r\n**Expected behavior:**\r\nNeed to send Peep with image or video data in it both to PeepEth server and to blockchain. \r\n\r\n**Solution:**\r\nIt’s needed to prepare sending data to server and Ethereum blockchain.\r\nCarefully look at how Peeps are sending now.\r\nSending controller is _SendPeepViewController_.\r\nAfter tapping \"Send\" button and writing correct password will be formed Server Peep:\r\n```swift\r\nlet peep = Peep(type: \"peep\",\r\n                content: content,\r\n                pic: \"\",\r\n                untrustedAddress: address!,\r\n                untrustedTimestamp: Int(Date().timeIntervalSince1970),\r\n                shareID: shareHash,\r\n                parentID: parentHash)\r\n\r\nlet createdServerPeep = CreateServerPeep(ipfs: \"xxx\",\r\n                                         author: address!,\r\n                                         content: content,\r\n                                         parentID: parentHash,\r\n                                         shareID: shareHash,\r\n                                         twitterShare: false,\r\n                                         picIpfs: \"\", // LOOK, its empty now. But it most likely shouldn't be\r\n                                         origContents: peep,\r\n                                         shareNow: true)\r\n```\r\nThen peep is posting to Peepeth server. In response you will get peeps hash from IPFS. In case of success you can optionally post peep to blockchain. But most likely you will not need to change anything further, since only a hash of a peep is required to send a transaction.\r\n\r\nPerhaps you need just to load image to some server and use its link when forming Peeps data. To get more info send Peep from Desktop PeepEth in Chrome using Developer Tools to “reverse engineer it”.\r\n\r\n**Acceptance Criteria:**\r\nThe code is written in new branch named feature/sendMedia or something like that.\r\nThe code implements the targets described above.\r\nThe code can be merged into the develop branch without conflicts.\r\n\r\n**Required Skill:**\r\nParticipants needs to have experience in Swift software development.","standard_bounties_id":2084,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":11,"github_org_name":"matterinc","github_repo_name":"PeepethClient","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:17.038496Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1698&network=mainnet","increase":"/issue/increase?pk=1698&network=mainnet","accept":"/issue/accept?pk=1698&network=mainnet","cancel":"/issue/cancel?pk=1698&network=mainnet","payout":"/issue/payout?pk=1698&network=mainnet","contribute":"/issue/contribute?pk=1698&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1698&network=mainnet","social_contribution":"/issue/social_contribution?pk=1698&network=mainnet","invoice":"/issue/invoice?pk=1698&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3420/2083","created_on":"2019-02-18T06:46:13.085960Z","modified_on":"2019-02-18T15:48:19.961107Z","title":"bug - 500 error / session value state missing ","web3_created":"2019-01-07T20:14:33Z","value_in_token":"300000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Bug","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/gitcoinco/web/issues/3420","github_comments":0,"bounty_owner_address":"0x00de4b13153673bcae2616b67bf822500d325fc3","bounty_owner_email":"kevin@gitcoin.co","bounty_owner_github_username":"owocki","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-06T20:14:33Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:46:14.213794Z","profile":{"id":1,"handle":"owocki","github_url":"https://github.com/owocki","avatar_url":"http://localhost:8000/dynamic/avatar/owocki","url":"/profile/owocki"},"metadata":{"new_bounty":{"id":1697,"title":"bug - 500 error / session value state missing ","token_name":"ETH","value_in_eth":"300000000000000000","value_in_token":"300000000000000000","value_in_usdt_now":"207.63","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:46:13.489082+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1697,"tip":null}],"keywords":"JavaScript, Python, HTML, CSS, Shell, Makefile, Dockerfile, Smarty","current_bounty":true,"value_in_eth":"300000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"207.63","value_in_usdt":"207.63","status":"open","now":"2019-02-18T16:03:19.804516Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"0.30","issue_description":"from @futrn on twitter:\r\n\r\n```\r\nI did a thing\r\n\r\nEssentially\r\n\r\nI ceyptotwitter feom my phone\r\nSaw the kudos\r\nWanted it\r\nNeeded web3\r\nSwitched over to trust\r\nLogged in to git\r\nThen sessions state eent missing\r\n\r\n#qa\r\n\r\nI went back home\r\n\r\nThen tried to login again\r\n\r\nIt must know im already logged in\r\n\r\nCuz it didnt asm for it again\r\n\r\n Logan [🗝🧙🏼‍♂️💻💰]\r\n But also just went back to 500\r\n\r\n4h\r\n```\r\n![foo](https://user-images.githubusercontent.com/513929/50709422-fcf08900-1024-11e9-9a1f-bf2a6bd78bda.jpg)\r\n\r\n\r\nfrom the context of his message, i'm assuming he's talking about him clicking the link on https://twitter.com/GetGitcoin/status/1081227999855337472","network":"mainnet","org_name":"gitcoinco","pk":1697,"issue_description_text":"from @futrn on twitter:\r\n\r\n```\r\nI did a thing\r\n\r\nEssentially\r\n\r\nI ceyptotwitter feom my phone\r\nSaw the kudos\r\nWanted it\r\nNeeded web3\r\nSwitched over to trust\r\nLogged in to git\r\nThen sessions state eent missing\r\n\r\n#qa\r\n\r\nI went back home\r\n\r\nThen tried to login again\r\n\r\nIt must know im already logged in\r\n\r\nCuz it didnt asm for it again\r\n\r\n Logan [🗝🧙🏼‍♂️💻💰]\r\n But also just went back to 500\r\n\r\n4h\r\n```\r\n![foo](https://user-images.githubusercontent.com/513929/50709422-fcf08900-1024-11e9-9a1f-bf2a6bd78bda.jpg)\r\n\r\n\r\nfrom the context of his message, i'm assuming he's talking about him clicking the link on https://twitter.com/GetGitcoin/status/1081227999855337472","standard_bounties_id":2083,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3420,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:19.978253Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1697&network=mainnet","increase":"/issue/increase?pk=1697&network=mainnet","accept":"/issue/accept?pk=1697&network=mainnet","cancel":"/issue/cancel?pk=1697&network=mainnet","payout":"/issue/payout?pk=1697&network=mainnet","contribute":"/issue/contribute?pk=1697&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1697&network=mainnet","social_contribution":"/issue/social_contribution?pk=1697&network=mainnet","invoice":"/issue/invoice?pk=1697&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/status-im/status.im/200/2079","created_on":"2019-02-18T06:45:57.371984Z","modified_on":"2019-02-18T15:48:20.742186Z","title":"Add support for Flow, Sequence, Mermaid and Math MD rendering","web3_created":"2019-01-07T09:47:26Z","value_in_token":"180000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/status-im/status.im/issues/200","github_comments":0,"bounty_owner_address":"0xa02378ca1c24767ecd776aafec02158a30dc01ac","bounty_owner_email":"statusgitcoin@gmail.com","bounty_owner_github_username":"StatusSceptre","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-06T09:47:26Z","activities":[],"keywords":"JavaScript, CSS, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"180.00","value_in_usdt":"180.00","status":"open","now":"2019-02-18T16:03:19.812949Z","avatar_url":"http://localhost:8000/dynamic/avatar/status-im","value_true":"180.00","issue_description":"See #156 for full details. This is a bounty to add support for more advanced MD rendering with the evetual goal of having our docs be able to render anything HackMD can.\r\n\r\nThe bounty is intended for @nanspro but if they don't claim it this week, we can open it to any and all comers.","network":"mainnet","org_name":"status-im","pk":1693,"issue_description_text":"See #156 for full details. This is a bounty to add support for more advanced MD rendering with the evetual goal of having our docs be able to render anything HackMD can.\r\n\r\nThe bounty is intended for @nanspro but if they don't claim it this week, we can open it to any and all comers.","standard_bounties_id":2079,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":200,"github_org_name":"status-im","github_repo_name":"status.im","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:20.764194Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1693&network=mainnet","increase":"/issue/increase?pk=1693&network=mainnet","accept":"/issue/accept?pk=1693&network=mainnet","cancel":"/issue/cancel?pk=1693&network=mainnet","payout":"/issue/payout?pk=1693&network=mainnet","contribute":"/issue/contribute?pk=1693&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1693&network=mainnet","social_contribution":"/issue/social_contribution?pk=1693&network=mainnet","invoice":"/issue/invoice?pk=1693&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"https://status.im/contribute/","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Status.im","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3427/2078","created_on":"2019-02-18T06:45:53.746201Z","modified_on":"2019-02-18T15:48:21.702244Z","title":"CODE - as a user attending ethdenver, i want to play the 'set completion' game at ETHDenver, so I can engage with sponsors and win a keep key","web3_created":"2019-01-06T18:14:42Z","value_in_token":"750000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/gitcoinco/web/issues/3427","github_comments":0,"bounty_owner_address":"0x00de4b13153673bcae2616b67bf822500d325fc3","bounty_owner_email":"kevin@gitcoin.co","bounty_owner_github_username":"owocki","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-13T18:14:42Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:45:54.925449Z","profile":{"id":1,"handle":"owocki","github_url":"https://github.com/owocki","avatar_url":"http://localhost:8000/dynamic/avatar/owocki","url":"/profile/owocki"},"metadata":{"new_bounty":{"id":1692,"title":"CODE - as a user attending ethdenver, i want to play the 'set completion' game at ETHDenver, so I can engage with sponsors and win a keep key","token_name":"ETH","value_in_eth":"750000000000000000","value_in_token":"750000000000000000","value_in_usdt_now":"519.08","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:45:54.020437+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1692,"tip":null}],"keywords":"JavaScript, Python, HTML, CSS, Shell, Makefile, Dockerfile, Smarty","current_bounty":true,"value_in_eth":"750000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"519.08","value_in_usdt":"519.08","status":"open","now":"2019-02-18T16:03:19.821380Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"0.75","issue_description":"<!--\r\nHello Gitcoiner!\r\n\r\nPlease use the template below for feature requests for Gitcoin.\r\nIf it is general support you need, reach out to us at\r\ngitcoin.co/slack\r\n\r\n-->\r\n\r\n### User Story\r\n\r\n[comment]: # (As a <user type>, I want to <task> so that <goal>.)\r\nas a user attending ethdenver, i want to play the 'set completion' game at ETHDenver, so I can engage with sponsors and win a keep key\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*:\r\n- John Paller wants it\r\n- To shill Kudos https://github.com/gitcoinco/kudosbadges/issues/124\r\n- To provide a bomb experience for engaging with sponsors at ETHDenver this year.\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*:\r\nFeature\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\n\r\nWe would like to build a set completion game for ETHDenver this year, wherein you complete various tasks for sponsors.  For each task you complete for a sponsor, you are given one of 12 limited edition [bufficorn kudos](https://github.com/gitcoinco/kudosbadges/issues/124).  \r\n\r\n[The technology for airdropping kudos already exists](https://github.com/gitcoinco/web/pull/2665)  We will give each sponsor a lint to airdrop their kudos.  [To see an example airdropped kudos, click here](https://gitcoin.co/kudos/redeem/holidaykudos1).\r\n\r\nWhat the user, who builds this ticket, will be responsible for, is the set completion aspect of the game.  Here's how it works.  \r\n\r\n1. User collects 12 bufficorn kudos\r\n2. User goes to gitcoin.co/ethdenver\r\n3. Site validates that user has all 12 bufficorn kudos (John to provide direction on whether we need to validate that they didn't get traded them or not.  i.e. do they need to come direct from our distribution address or not?)\r\n4. If validation in step 3 passes, then user is sent a special 13th Kudos.\r\n5. If validation in step 3 passes, then user is sent a uPort attestation that they've finished the ETHdenver prize.\r\n6. If validation in step 3 passes, then user is sent a uPort attestation they get a kudos\r\n\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\n\r\nThis bounty will be broken up into three components, \r\n\r\n1. design for gitcoin.co/ethdenver\r\n1. html coding for gitcoin.co/ethdenver\r\n2. functional coding for gitcoin.co/ethdenver\r\n\r\nThe scope of THIS SPECIFIC coding task is to just do the html / frontend coding.  Acceptance criteria:\r\n\r\n* All of the designs are coded.\r\n* all pages are responsive\r\n* pls allow 2-3 iterations of feedback.\r\n* must be submitted by 1/11/2019\r\n\r\n### Designs\r\n\r\nNot logged in:\r\n![not logged in copy](https://user-images.githubusercontent.com/19514207/50601723-ff9d9200-0eef-11e9-9d7c-5671aab6e8ec.jpg)\r\n\r\nLogged in:\r\n![logged in](https://user-images.githubusercontent.com/19514207/50601804-3673a800-0ef0-11e9-8c2d-614bc3bcfbbc.jpg)\r\n\r\nCompleted:\r\n![completed](https://user-images.githubusercontent.com/19514207/50601806-396e9880-0ef0-11e9-95fa-7c21d9099c69.jpg)\r\n\r\nEDIT : Per convo with @kuhnchris on 1/11 at https://github.com/gitcoinco/web/issues/3197#issuecomment-453560570 , we are going to extend this ticket to contiain the scope of all coding tasks.  We will use the architecture proposed at https://github.com/gitcoinco/web/issues/3197#issuecomment-453560570 and will aim to get it done by 1/14.","network":"mainnet","org_name":"gitcoinco","pk":1692,"issue_description_text":"### User Story\r\n\r\n[comment]: # (As a , I want to  so that .)\r\nas a user attending ethdenver, i want to play the 'set completion' game at ETHDenver, so I can engage with sponsors and win a keep key\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*:\r\n- John Paller wants it\r\n- To shill Kudos https://github.com/gitcoinco/kudosbadges/issues/124\r\n- To provide a bomb experience for engaging with sponsors at ETHDenver this year.\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*:\r\nFeature\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\n\r\nWe would like to build a set completion game for ETHDenver this year, wherein you complete various tasks for sponsors.  For each task you complete for a sponsor, you are given one of 12 limited edition [bufficorn kudos](https://github.com/gitcoinco/kudosbadges/issues/124).  \r\n\r\n[The technology for airdropping kudos already exists](https://github.com/gitcoinco/web/pull/2665)  We will give each sponsor a lint to airdrop their kudos.  [To see an example airdropped kudos, click here](https://gitcoin.co/kudos/redeem/holidaykudos1).\r\n\r\nWhat the user, who builds this ticket, will be responsible for, is the set completion aspect of the game.  Here's how it works.  \r\n\r\n1. User collects 12 bufficorn kudos\r\n2. User goes to gitcoin.co/ethdenver\r\n3. Site validates that user has all 12 bufficorn kudos (John to provide direction on whether we need to validate that they didn't get traded them or not.  i.e. do they need to come direct from our distribution address or not?)\r\n4. If validation in step 3 passes, then user is sent a special 13th Kudos.\r\n5. If validation in step 3 passes, then user is sent a uPort attestation that they've finished the ETHdenver prize.\r\n6. If validation in step 3 passes, then user is sent a uPort attestation they get a kudos\r\n\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\n\r\nThis bounty will be broken up into three components, \r\n\r\n1. design for gitcoin.co/ethdenver\r\n1. html coding for gitcoin.co/ethdenver\r\n2. functional coding for gitcoin.co/ethdenver\r\n\r\nThe scope of THIS SPECIFIC coding task is to just do the html / frontend coding.  Acceptance criteria:\r\n\r\n* All of the designs are coded.\r\n* all pages are responsive\r\n* pls allow 2-3 iterations of feedback.\r\n* must be submitted by 1/11/2019\r\n\r\n### Designs\r\n\r\nNot logged in:\r\n![not logged in copy](https://user-images.githubusercontent.com/19514207/50601723-ff9d9200-0eef-11e9-9d7c-5671aab6e8ec.jpg)\r\n\r\nLogged in:\r\n![logged in](https://user-images.githubusercontent.com/19514207/50601804-3673a800-0ef0-11e9-8c2d-614bc3bcfbbc.jpg)\r\n\r\nCompleted:\r\n![completed](https://user-images.githubusercontent.com/19514207/50601806-396e9880-0ef0-11e9-95fa-7c21d9099c69.jpg)\r\n\r\nEDIT : Per convo with @kuhnchris on 1/11 at https://github.com/gitcoinco/web/issues/3197#issuecomment-453560570 , we are going to extend this ticket to contiain the scope of all coding tasks.  We will use the architecture proposed at https://github.com/gitcoinco/web/issues/3197#issuecomment-453560570 and will aim to get it done by 1/14.","standard_bounties_id":2078,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3427,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:21.722991Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1692&network=mainnet","increase":"/issue/increase?pk=1692&network=mainnet","accept":"/issue/accept?pk=1692&network=mainnet","cancel":"/issue/cancel?pk=1692&network=mainnet","payout":"/issue/payout?pk=1692&network=mainnet","contribute":"/issue/contribute?pk=1692&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1692&network=mainnet","social_contribution":"/issue/social_contribution?pk=1692&network=mainnet","invoice":"/issue/invoice?pk=1692&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"https://boards.greenhouse.io/consensys/jobs/1333457","needs_review":[],"github_issue_state":"closed","is_issue_closed":true,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/HERCone/restful-hipr/1/2077","created_on":"2019-02-18T06:45:51.126999Z","modified_on":"2019-02-18T15:48:22.805056Z","title":"Create Games on Top of Restful HIPR API ","web3_created":"2019-01-06T16:54:52Z","value_in_token":"500000000000000000000.00","token_name":"HERC","token_address":"0x6251583e7d997df3604bc73b9779196e94a090ce","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/HERCone/restful-hipr/issues/1","github_comments":0,"bounty_owner_address":"0x96706eb471f875a9a41442f358d3b34ba02f868b","bounty_owner_email":"logan@herc.one","bounty_owner_github_username":"lrgeoemtry","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-13T16:54:52Z","activities":[],"keywords":"JavaScript, HTML, Shell, CSS, Unity, Ethereum, ","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.830479Z","avatar_url":"http://localhost:8000/dynamic/avatar/HERCone","value_true":"0.00","issue_description":"Hello Everyone and Welcome to a Funded Issue Grant! \r\n\r\nThis is a come one come all to become a part of the HIPR Games experience. \r\n\r\nWe have provided the framework for a Gamified Internal Control in which data can be checksummed and verified that they are the same. \r\n\r\nIf you have any questions regarding how or why please refer to the documents found on herc.one or skip over to hipr.one in a web3 browser to see our first game. \r\n\r\nyou can also see the open source at https://github.com/hercone/hipr for our preferred unity environment :) \r\n\r\n\r\nGood Luck!  ","network":"mainnet","org_name":"HERCone","pk":1691,"issue_description_text":"Hello Everyone and Welcome to a Funded Issue Grant! \r\n\r\nThis is a come one come all to become a part of the HIPR Games experience. \r\n\r\nWe have provided the framework for a Gamified Internal Control in which data can be checksummed and verified that they are the same. \r\n\r\nIf you have any questions regarding how or why please refer to the documents found on herc.one or skip over to hipr.one in a web3 browser to see our first game. \r\n\r\nyou can also see the open source at https://github.com/hercone/hipr for our preferred unity environment :) \r\n\r\n\r\nGood Luck!","standard_bounties_id":2077,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":1,"github_org_name":"HERCone","github_repo_name":"restful-hipr","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:22.819739Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1691&network=mainnet","increase":"/issue/increase?pk=1691&network=mainnet","accept":"/issue/accept?pk=1691&network=mainnet","cancel":"/issue/cancel?pk=1691&network=mainnet","payout":"/issue/payout?pk=1691&network=mainnet","contribute":"/issue/contribute?pk=1691&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1691&network=mainnet","social_contribution":"/issue/social_contribution?pk=1691&network=mainnet","invoice":"/issue/invoice?pk=1691&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"https://herc.one/careers","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Hercules SEZC","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ark-mod/ArkBot/86/2074","created_on":"2019-02-18T06:45:32.967274Z","modified_on":"2019-02-18T15:48:23.639872Z","title":"Atlas bot","web3_created":"2019-01-05T15:31:21Z","value_in_token":"459000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ark-mod/ArkBot/issues/86","github_comments":0,"bounty_owner_address":"0x25777d544577d7a29e51c35e02fe8dba40d9786a","bounty_owner_email":"jefferson@jeffersonnunnconsulting.com","bounty_owner_github_username":"jefferson-1","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-04T15:31:21Z","activities":[],"keywords":"C++, JSON","current_bounty":true,"value_in_eth":"459000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"318.37","value_in_usdt":"318.37","status":"open","now":"2019-02-18T16:03:19.837189Z","avatar_url":"http://localhost:8000/dynamic/avatar/ark-mod","value_true":"0.46","issue_description":"Apologies posting here, please close once you have reviewed. I know little about this language, but do you think this could be forked and adapted to run with Atlas, if only the discord bot element for updating/restarting servers? \r\nare there any plans to do this?","network":"mainnet","org_name":"ark-mod","pk":1689,"issue_description_text":"Apologies posting here, please close once you have reviewed. I know little about this language, but do you think this could be forked and adapted to run with Atlas, if only the discord bot element for updating/restarting servers? \r\nare there any plans to do this?","standard_bounties_id":2074,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":86,"github_org_name":"ark-mod","github_repo_name":"ArkBot","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:23.655706Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1689&network=mainnet","increase":"/issue/increase?pk=1689&network=mainnet","accept":"/issue/accept?pk=1689&network=mainnet","cancel":"/issue/cancel?pk=1689&network=mainnet","payout":"/issue/payout?pk=1689&network=mainnet","contribute":"/issue/contribute?pk=1689&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1689&network=mainnet","social_contribution":"/issue/social_contribution?pk=1689&network=mainnet","invoice":"/issue/invoice?pk=1689&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Knights","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/trailofbits/slither/101/2073","created_on":"2019-02-18T06:45:29.865941Z","modified_on":"2019-02-18T15:48:24.335194Z","title":"Printer/external tool: Finding code similarity ","web3_created":"2019-01-04T19:27:28Z","value_in_token":"160000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/trailofbits/slither/issues/101","github_comments":0,"bounty_owner_address":"0x9ace976f2f06f2d2815a93f1866011007171fdb2","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-03T19:27:28Z","activities":[],"keywords":"Python, Solidity, Shell, Dockerfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"160.00","value_in_usdt":"160.00","status":"open","now":"2019-02-18T16:03:19.842984Z","avatar_url":"http://localhost:8000/dynamic/avatar/trailofbits","value_true":"160.00","issue_description":"Given two codebases, slither should be able to detect the similar functions/contracts\r\n\r\nA naive approach could be to only compare the AST of the functions.\r\n\r\nWe can also have a more sophisticated approach, where we abstract the name of the variables/functions and compare an high-level signature of the functions.  The academic literature is rich on this domain, so this work could lead to even more experimental solutions (ex: using machine learning to build a similarity metric, ...), but the naive approach should be the first step.\r\n\r\nThe solution can be implemented as a printer, or as an external tool. It would be nice to be able to build a large database of similar functions/contracts across multiples projects.\r\n\r\nIt migh also be useful for code review (ex: if someone uses a slightly modified version of SafeMath, the code needs additional consideration)  \r\n\r\nI am open to any suggestions/ideas\r\n\r\n","network":"mainnet","org_name":"trailofbits","pk":1688,"issue_description_text":"Given two codebases, slither should be able to detect the similar functions/contracts\r\n\r\nA naive approach could be to only compare the AST of the functions.\r\n\r\nWe can also have a more sophisticated approach, where we abstract the name of the variables/functions and compare an high-level signature of the functions.  The academic literature is rich on this domain, so this work could lead to even more experimental solutions (ex: using machine learning to build a similarity metric, ...), but the naive approach should be the first step.\r\n\r\nThe solution can be implemented as a printer, or as an external tool. It would be nice to be able to build a large database of similar functions/contracts across multiples projects.\r\n\r\nIt migh also be useful for code review (ex: if someone uses a slightly modified version of SafeMath, the code needs additional consideration)  \r\n\r\nI am open to any suggestions/ideas","standard_bounties_id":2073,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":101,"github_org_name":"trailofbits","github_repo_name":"slither","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:24.351960Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1688&network=mainnet","increase":"/issue/increase?pk=1688&network=mainnet","accept":"/issue/accept?pk=1688&network=mainnet","cancel":"/issue/cancel?pk=1688&network=mainnet","payout":"/issue/payout?pk=1688&network=mainnet","contribute":"/issue/contribute?pk=1688&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1688&network=mainnet","social_contribution":"/issue/social_contribution?pk=1688&network=mainnet","invoice":"/issue/invoice?pk=1688&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/matterinc/web3swift/103/2072","created_on":"2019-02-18T06:45:27.168799Z","modified_on":"2019-02-18T15:48:25.342064Z","title":"Support ST-20","web3_created":"2019-01-04T19:14:17Z","value_in_token":"60000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/matterinc/web3swift/issues/103","github_comments":0,"bounty_owner_address":"0x9ace976f2f06f2d2815a93f1866011007171fdb2","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-03T19:14:17Z","activities":[],"keywords":"JavaScript, Swift, Ruby, Objective-C, C","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"60.00","value_in_usdt":"60.00","status":"open","now":"2019-02-18T16:03:19.851131Z","avatar_url":"http://localhost:8000/dynamic/avatar/matterinc","value_true":"60.00","issue_description":"ST-20 token is an Ethereum-based token implemented on top of the ERC-20 protocol that adds the ability for tokens to control transfers based on specific rules. \r\nIts description: https://github.com/PolymathNetwork/polymath-core.\r\nLook at how there are implemented ERC-20 and ERC-721 in https://github.com/matterinc/web3swift/tree/develop/web3swift/PrecompiledContracts.","network":"mainnet","org_name":"matterinc","pk":1687,"issue_description_text":"ST-20 token is an Ethereum-based token implemented on top of the ERC-20 protocol that adds the ability for tokens to control transfers based on specific rules. \r\nIts description: https://github.com/PolymathNetwork/polymath-core.\r\nLook at how there are implemented ERC-20 and ERC-721 in https://github.com/matterinc/web3swift/tree/develop/web3swift/PrecompiledContracts.","standard_bounties_id":2072,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":103,"github_org_name":"matterinc","github_repo_name":"web3swift","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:25.356356Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1687&network=mainnet","increase":"/issue/increase?pk=1687&network=mainnet","accept":"/issue/accept?pk=1687&network=mainnet","cancel":"/issue/cancel?pk=1687&network=mainnet","payout":"/issue/payout?pk=1687&network=mainnet","contribute":"/issue/contribute?pk=1687&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1687&network=mainnet","social_contribution":"/issue/social_contribution?pk=1687&network=mainnet","invoice":"/issue/invoice?pk=1687&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/status-im/status-react/7204/2070","created_on":"2019-02-18T06:45:21.212466Z","modified_on":"2019-02-18T15:48:26.135443Z","title":"Add extension event to sign transaction data","web3_created":"2019-01-03T19:33:06Z","value_in_token":"300000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/status-im/status-react/issues/7204","github_comments":0,"bounty_owner_address":"0xa02378ca1c24767ecd776aafec02158a30dc01ac","bounty_owner_email":"statusgitcoin@gmail.com","bounty_owner_github_username":"StatusSceptre","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-07-02T19:33:06Z","activities":[],"keywords":"Clojure, Python, Objective-C, Shell, C++, Java, NSIS, JavaScript, CMake, Groovy, Dockerfile, Ruby, Makefile, QML, C, Batchfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"300.00","value_in_usdt":"300.00","status":"open","now":"2019-02-18T16:03:19.859936Z","avatar_url":"http://localhost:8000/dynamic/avatar/status-im","value_true":"300.00","issue_description":"### User Story\r\n\r\nAs a developer, I want an [extension](https://status.im/extensions/) event to sign transaction details as hex. The signed data can then be sent to a remote relayer that will be able to send the transaction to the blockchain using [eth_sendRawTransaction](https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sendrawtransaction)\r\n\r\nThis will require changes to `status-go`.\r\n\r\nSee some potential hints to implement this: https://ethereum.stackexchange.com/questions/3386/create-and-sign-offline-raw-transactions/3401#3401\r\n\r\n### Description\r\n\r\n*Type*: Feature\r\n\n\n<blockquote><img src=\"https://cdn.sstatic.net/Sites/ethereum/img/apple-touch-icon@2.png?v=fcf6615497f4\" width=\"48\" align=\"right\"><div>Ethereum Stack Exchange</div><div><strong><a href=\"https://ethereum.stackexchange.com/questions/3386/create-and-sign-offline-raw-transactions/3401\">Create and sign OFFLINE raw transactions?</a></strong></div><div>I'm looking to create a raw transaction, sign it, and broadcast it using the eth.sendRawTransaction RPC method.\n\nI would like to do this offline using code or an open-source library OR online but w...</div></blockquote>","network":"mainnet","org_name":"status-im","pk":1685,"issue_description_text":"### User Story\r\n\r\nAs a developer, I want an [extension](https://status.im/extensions/) event to sign transaction details as hex. The signed data can then be sent to a remote relayer that will be able to send the transaction to the blockchain using [eth_sendRawTransaction](https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sendrawtransaction)\r\n\r\nThis will require changes to `status-go`.\r\n\r\nSee some potential hints to implement this: https://ethereum.stackexchange.com/questions/3386/create-and-sign-offline-raw-transactions/3401#3401\r\n\r\n### Description\r\n\r\n*Type*: Feature\r\n\n\nEthereum Stack ExchangeCreate and sign OFFLINE raw transactions?I'm looking to create a raw transaction, sign it, and broadcast it using the eth.sendRawTransaction RPC method.\n\nI would like to do this offline using code or an open-source library OR online but w...","standard_bounties_id":2070,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":7204,"github_org_name":"status-im","github_repo_name":"status-react","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:26.149180Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1685&network=mainnet","increase":"/issue/increase?pk=1685&network=mainnet","accept":"/issue/accept?pk=1685&network=mainnet","cancel":"/issue/cancel?pk=1685&network=mainnet","payout":"/issue/payout?pk=1685&network=mainnet","contribute":"/issue/contribute?pk=1685&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1685&network=mainnet","social_contribution":"/issue/social_contribution?pk=1685&network=mainnet","invoice":"/issue/invoice?pk=1685&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3370/2064","created_on":"2019-02-18T06:44:57.079087Z","modified_on":"2019-02-18T15:48:26.850747Z","title":"As a user, I want Gitcoin migrated over to new the new Infura Dashboard, so that Gitcoin continues to work after they deprecate public access","web3_created":"2019-01-02T19:57:29Z","value_in_token":"500000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/gitcoinco/web/issues/3370","github_comments":0,"bounty_owner_address":"0x00de4b13153673bcae2616b67bf822500d325fc3","bounty_owner_email":"kevin@gitcoin.co","bounty_owner_github_username":"owocki","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2020-01-02T19:57:29Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:44:58.105657Z","profile":{"id":1,"handle":"owocki","github_url":"https://github.com/owocki","avatar_url":"http://localhost:8000/dynamic/avatar/owocki","url":"/profile/owocki"},"metadata":{"new_bounty":{"id":1679,"title":"As a user, I want Gitcoin migrated over to new the new Infura Dashboard, so that Gitcoin continues to work after they deprecate public access","token_name":"ETH","value_in_eth":"500000000000000000","value_in_token":"500000000000000000","value_in_usdt_now":"346.05","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:44:57.350891+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1679,"tip":null}],"keywords":"JavaScript, Python, HTML, CSS, Shell, Makefile, Dockerfile, Smarty","current_bounty":true,"value_in_eth":"500000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"346.05","value_in_usdt":"346.05","status":"open","now":"2019-02-18T16:03:19.868761Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"0.50","issue_description":"<!--\r\nHello Gitcoiner!\r\n\r\nPlease use the template below for feature requests for Gitcoin.\r\nIf it is general support you need, reach out to us at\r\ngitcoin.co/slack\r\n\r\n-->\r\n\r\n### User Story\r\n\r\n[comment]: # (As a <user type>, I want to <task> so that <goal>.)\r\nAs a user, I want Gitcoin migrated over to new the new Infura Dashboard, so that Gitcoin continues to work after they deprecate public access\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*:\r\nSo gitcoin continues to work\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*:\r\nFeature\r\n\r\n### Current Behavior\r\n[comment]: # (Describe what actually happened.)\r\nPublic Infura APIS\r\n\r\n### Expected Behavior\r\n[comment]: # (Describe what you expected to happen.)\r\nPermissioned Infura APIs\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\n\r\n* All gitcoin API calls through the frontend are piped through the new Infura API\r\n* All gitcoin API calls through the backedn are piped through the new Infura API\r\n* Gitcoin Bounty, Tip, Kudos, and Grants calls are piped through the Infura API.\r\n\r\nPlease submit a working PR by January 5th 2019, and expect 2-3 iterations via code review after that.\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\nhttps://blog.infura.io/introducing-the-infura-dashboard-8969b7ab94e7\r\n\r\nNote, Gitcoin Grants is the only product that uses dynamic smart contracts.  We are still searching for a way to dynamically provision smart contract API access via infura.  See below:\r\n\r\n\r\n<img width=\"1208\" alt=\"screen shot 2019-01-02 at 9 22 03 am\" src=\"https://user-images.githubusercontent.com/513929/50600936-e9e88800-0e6f-11e9-8908-ee74e4b6dbdc.png\">\r\n\r\n","network":"mainnet","org_name":"gitcoinco","pk":1679,"issue_description_text":"### User Story\r\n\r\n[comment]: # (As a , I want to  so that .)\r\nAs a user, I want Gitcoin migrated over to new the new Infura Dashboard, so that Gitcoin continues to work after they deprecate public access\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*:\r\nSo gitcoin continues to work\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*:\r\nFeature\r\n\r\n### Current Behavior\r\n[comment]: # (Describe what actually happened.)\r\nPublic Infura APIS\r\n\r\n### Expected Behavior\r\n[comment]: # (Describe what you expected to happen.)\r\nPermissioned Infura APIs\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\n\r\n* All gitcoin API calls through the frontend are piped through the new Infura API\r\n* All gitcoin API calls through the backedn are piped through the new Infura API\r\n* Gitcoin Bounty, Tip, Kudos, and Grants calls are piped through the Infura API.\r\n\r\nPlease submit a working PR by January 5th 2019, and expect 2-3 iterations via code review after that.\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\nhttps://blog.infura.io/introducing-the-infura-dashboard-8969b7ab94e7\r\n\r\nNote, Gitcoin Grants is the only product that uses dynamic smart contracts.  We are still searching for a way to dynamically provision smart contract API access via infura.  See below:","standard_bounties_id":2064,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3370,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:26.870887Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1679&network=mainnet","increase":"/issue/increase?pk=1679&network=mainnet","accept":"/issue/accept?pk=1679&network=mainnet","cancel":"/issue/cancel?pk=1679&network=mainnet","payout":"/issue/payout?pk=1679&network=mainnet","contribute":"/issue/contribute?pk=1679&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1679&network=mainnet","social_contribution":"/issue/social_contribution?pk=1679&network=mainnet","invoice":"/issue/invoice?pk=1679&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"https://boards.greenhouse.io/consensys/jobs/1333457","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/austintgriffith/burner-wallet/51/2059","created_on":"2019-02-18T06:44:41.674336Z","modified_on":"2019-02-18T15:48:27.562622Z","title":"Burner Wallet Loading Gif","web3_created":"2018-12-31T05:38:27Z","value_in_token":"50000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/austintgriffith/burner-wallet/issues/51","github_comments":0,"bounty_owner_address":"0x87ac0c28fc8095e74474bab74cc6368480a20a49","bounty_owner_email":"austin@concurrence.io","bounty_owner_github_username":"austintgriffith","bounty_owner_name":"Anonymous","fulfillments":[{"fulfiller_address":"0xFF16d64179A02D6a56a1183A28f1D6293646E2dd","fulfiller_email":"valedictorian2004@gmail.com","fulfiller_github_username":"plor","fulfiller_name":"","fulfillment_id":1,"accepted":false,"profile":null,"created_on":"2019-02-18T06:44:42.685780Z","accepted_on":null,"fulfiller_github_url":"https://github.com/austintgriffith/burner-wallet/issues/51#issuecomment-452400816"},{"fulfiller_address":"0x7c49ec8AF145efD8f7f8b3EBD7c9016984761Fc3","fulfiller_email":"andresberejnoi@gmail.com","fulfiller_github_username":"andresberejnoi","fulfiller_name":"","fulfillment_id":0,"accepted":false,"profile":null,"created_on":"2019-02-18T06:44:42.681186Z","accepted_on":null,"fulfiller_github_url":""}],"interested":[],"is_open":true,"expires_date":"2019-01-14T05:38:27Z","activities":[],"keywords":"design animated gif burner wallet","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"50.00","value_in_usdt":"50.00","status":"open","now":"2019-02-18T16:03:19.882639Z","avatar_url":"http://localhost:8000/dynamic/avatar/austintgriffith","value_true":"50.00","issue_description":"Create a bad ass loader gif for the burner wallet. \r\n\r\nThere are moments when you are waiting for the Burner to scan QR code or send a transaction. \r\n\r\nRight now there is a filler loader but let's create something awesome. \r\n\r\nIt would be cool if it was \"burner\" / \"cypherpunk\" themed maybe even one that is qr code themed \r\n\r\nIt should be around 150px x 150px and still load quickly on old phones ","network":"mainnet","org_name":"austintgriffith","pk":1675,"issue_description_text":"Create a bad ass loader gif for the burner wallet. \r\n\r\nThere are moments when you are waiting for the Burner to scan QR code or send a transaction. \r\n\r\nRight now there is a filler loader but let's create something awesome. \r\n\r\nIt would be cool if it was \"burner\" / \"cypherpunk\" themed maybe even one that is qr code themed \r\n\r\nIt should be around 150px x 150px and still load quickly on old phones","standard_bounties_id":2059,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":51,"github_org_name":"austintgriffith","github_repo_name":"burner-wallet","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:27.577038Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":"2019-02-18T06:44:42.681186Z","fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1675&network=mainnet","increase":"/issue/increase?pk=1675&network=mainnet","accept":"/issue/accept?pk=1675&network=mainnet","cancel":"/issue/cancel?pk=1675&network=mainnet","payout":"/issue/payout?pk=1675&network=mainnet","contribute":"/issue/contribute?pk=1675&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1675&network=mainnet","social_contribution":"/issue/social_contribution?pk=1675&network=mainnet","invoice":"/issue/invoice?pk=1675&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/matterinc/web3swift/101/2055","created_on":"2019-02-18T06:44:26.284895Z","modified_on":"2019-02-18T15:48:30.802048Z","title":"Support SRC-20","web3_created":"2018-12-27T17:37:35Z","value_in_token":"100000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/matterinc/web3swift/issues/101","github_comments":0,"bounty_owner_address":"0x9ace976f2f06f2d2815a93f1866011007171fdb2","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-26T17:37:35Z","activities":[],"keywords":"JavaScript, Swift, Ruby, Objective-C, C","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"100.00","value_in_usdt":"100.00","status":"open","now":"2019-02-18T16:03:19.892047Z","avatar_url":"http://localhost:8000/dynamic/avatar/matterinc","value_true":"100.00","issue_description":"Swarm is developing SRC20, the protocol that enables the tokenization of assets on the blockchain.\r\nLook at how there are implemented ERC-20 and ERC-721 in https://github.com/matterinc/web3swift/tree/develop/web3swift/PrecompiledContracts.","network":"mainnet","org_name":"matterinc","pk":1671,"issue_description_text":"Swarm is developing SRC20, the protocol that enables the tokenization of assets on the blockchain.\r\nLook at how there are implemented ERC-20 and ERC-721 in https://github.com/matterinc/web3swift/tree/develop/web3swift/PrecompiledContracts.","standard_bounties_id":2055,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":101,"github_org_name":"matterinc","github_repo_name":"web3swift","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:30.816790Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1671&network=mainnet","increase":"/issue/increase?pk=1671&network=mainnet","accept":"/issue/accept?pk=1671&network=mainnet","cancel":"/issue/cancel?pk=1671&network=mainnet","payout":"/issue/payout?pk=1671&network=mainnet","contribute":"/issue/contribute?pk=1671&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1671&network=mainnet","social_contribution":"/issue/social_contribution?pk=1671&network=mainnet","invoice":"/issue/invoice?pk=1671&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"closed","is_issue_closed":true,"additional_funding_summary":{},"funding_organisation":"ECF","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/trezor/trezor-android/29/2052","created_on":"2019-02-18T06:44:16.213654Z","modified_on":"2019-02-18T15:48:31.586141Z","title":"Replace protobuf client implementation with wire","web3_created":"2018-12-26T20:18:15Z","value_in_token":"150000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/trezor/trezor-android/issues/29","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-26T20:18:15Z","activities":[],"keywords":"Java, Shell","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"150.00","value_in_usdt":"150.00","status":"open","now":"2019-02-18T16:03:19.900824Z","avatar_url":"http://localhost:8000/dynamic/avatar/trezor","value_true":"150.00","issue_description":"Protobuf is still quite heavy - especially method-count wise - perhaps (opinions welcome - cc @prusnak) we should replace it with wire: \r\nhttps://github.com/square/wire","network":"mainnet","org_name":"trezor","pk":1668,"issue_description_text":"Protobuf is still quite heavy - especially method-count wise - perhaps (opinions welcome - cc @prusnak) we should replace it with wire: \r\nhttps://github.com/square/wire","standard_bounties_id":2052,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":29,"github_org_name":"trezor","github_repo_name":"trezor-android","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:31.598996Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1668&network=mainnet","increase":"/issue/increase?pk=1668&network=mainnet","accept":"/issue/accept?pk=1668&network=mainnet","cancel":"/issue/cancel?pk=1668&network=mainnet","payout":"/issue/payout?pk=1668&network=mainnet","contribute":"/issue/contribute?pk=1668&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1668&network=mainnet","social_contribution":"/issue/social_contribution?pk=1668&network=mainnet","invoice":"/issue/invoice?pk=1668&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/42wim/matterbridge/663/2051","created_on":"2019-02-18T06:44:12.889553Z","modified_on":"2019-02-18T15:48:32.931577Z","title":"[Riot/matrix] Support for markdown by supporting Riot's formatted_body tag","web3_created":"2018-12-26T13:40:52Z","value_in_token":"100000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/42wim/matterbridge/issues/663","github_comments":0,"bounty_owner_address":"0x701d0ecb3ba780de7b2b36789aec4493a426010a","bounty_owner_email":"kay@giveth.io","bounty_owner_github_username":"geleeroyale","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-26T13:40:52Z","activities":[],"keywords":"Go, Riot, matrix","current_bounty":true,"value_in_eth":"100000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"69.21","value_in_usdt":"69.21","status":"open","now":"2019-02-18T16:03:19.909961Z","avatar_url":"http://localhost:8000/dynamic/avatar/42wim","value_true":"0.10","issue_description":"**Is your feature request related to a problem? Please describe.**\r\nWhen a message containing markdown is sent to Riot from anothe client (tested with rocket chat) - the markdown is not parsed correctly, as it renders the literal input like in the following example:\r\n\r\n![riot-rocket](https://user-images.githubusercontent.com/317685/50447367-ee1a2000-091a-11e9-8e0c-8bbf53419011.png)\r\n\r\n**Describe the solution you'd like**\r\nI posted this as a question in #matterbridge:matrix.org - I am out of my depth here, but wim answered the following:\r\n<w​im> \r\ni think riot replaces clientside markdown input to commonmark, haven't looked into this.\r\n```\r\n{\"body\":\"*def*\", \"format\":\"org.matrix.custom.html\", \"formatted_body\":\"<em>def</em>\", \"msgtype\":\"m.text\"}\r\n```\r\n\r\n**Describe alternatives you've considered**\r\nI considered other bridging solutions, but there does not seem to be anything ready for deployment to bridge rocket chat and Riot.\r\n\r\n**Additional context**\r\nI love matterbridge and the versatility it brings to bridging chat protocols. I am heavily advocating it and use it to bridge some rooms of our communities +giveth:matrix.org and +aragon:matrix.org between Telegram/Riot/rocket chat and in the past Slack.\r\n","network":"mainnet","org_name":"42wim","pk":1667,"issue_description_text":"**Is your feature request related to a problem? Please describe.**\r\nWhen a message containing markdown is sent to Riot from anothe client (tested with rocket chat) - the markdown is not parsed correctly, as it renders the literal input like in the following example:\r\n\r\n![riot-rocket](https://user-images.githubusercontent.com/317685/50447367-ee1a2000-091a-11e9-8e0c-8bbf53419011.png)\r\n\r\n**Describe the solution you'd like**\r\nI posted this as a question in #matterbridge:matrix.org - I am out of my depth here, but wim answered the following:\r\n \r\ni think riot replaces clientside markdown input to commonmark, haven't looked into this.\r\n```\r\n{\"body\":\"*def*\", \"format\":\"org.matrix.custom.html\", \"formatted_body\":\"def\", \"msgtype\":\"m.text\"}\r\n```\r\n\r\n**Describe alternatives you've considered**\r\nI considered other bridging solutions, but there does not seem to be anything ready for deployment to bridge rocket chat and Riot.\r\n\r\n**Additional context**\r\nI love matterbridge and the versatility it brings to bridging chat protocols. I am heavily advocating it and use it to bridge some rooms of our communities +giveth:matrix.org and +aragon:matrix.org between Telegram/Riot/rocket chat and in the past Slack.","standard_bounties_id":2051,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":663,"github_org_name":"42wim","github_repo_name":"matterbridge","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:32.955188Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1667&network=mainnet","increase":"/issue/increase?pk=1667&network=mainnet","accept":"/issue/accept?pk=1667&network=mainnet","cancel":"/issue/cancel?pk=1667&network=mainnet","payout":"/issue/payout?pk=1667&network=mainnet","contribute":"/issue/contribute?pk=1667&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1667&network=mainnet","social_contribution":"/issue/social_contribution?pk=1667&network=mainnet","invoice":"/issue/invoice?pk=1667&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"closed","is_issue_closed":true,"additional_funding_summary":{},"funding_organisation":"Aragon DAC","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/centrifuge/precise-proofs/34/2049","created_on":"2019-02-18T06:44:04.292041Z","modified_on":"2019-02-18T15:48:33.889113Z","title":"Create converter to/from numerical and string properties","web3_created":"2018-12-25T17:50:49Z","value_in_token":"280000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/centrifuge/precise-proofs/issues/34","github_comments":0,"bounty_owner_address":"0x52ec80600642cedde9de1f570335481c348be74c","bounty_owner_email":"l@lucasvo.com","bounty_owner_github_username":"lucasvo","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-24T17:50:49Z","activities":[],"keywords":"Go, Makefile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"280.00","value_in_usdt":"280.00","status":"open","now":"2019-02-18T16:03:19.918990Z","avatar_url":"http://localhost:8000/dynamic/avatar/centrifuge","value_true":"280.00","issue_description":"We should create a helper that can take a binary property and convert it to a literal property without having an instance of the message available but only the type. The converter needs to be smart enough to concatenate nested fields and repeated fields.\r\n\r\nAcceptance Criteria:\r\n1) A method is added to the proofs package that accepts a literal property `string`, a protobuf autogenerated struct type and returns the compact property as `[]byte`\r\n2) A method is added to the proofs package that accepts a compact property `[]byte`, a protobuf autogenerated struct type and returns a literal property as `string`\r\n3) There is adequate test coverage for the above two methods\r\n4) The example is extended with an example usage (https://github.com/centrifuge/precise-proofs/blob/master/proofs/tree_test.go#L1351)\r\n\r\nFor more info on literal types and it's implementation see \r\nhttps://github.com/centrifuge/precise-proofs/issues/29","network":"mainnet","org_name":"centrifuge","pk":1665,"issue_description_text":"We should create a helper that can take a binary property and convert it to a literal property without having an instance of the message available but only the type. The converter needs to be smart enough to concatenate nested fields and repeated fields.\r\n\r\nAcceptance Criteria:\r\n1) A method is added to the proofs package that accepts a literal property `string`, a protobuf autogenerated struct type and returns the compact property as `[]byte`\r\n2) A method is added to the proofs package that accepts a compact property `[]byte`, a protobuf autogenerated struct type and returns a literal property as `string`\r\n3) There is adequate test coverage for the above two methods\r\n4) The example is extended with an example usage (https://github.com/centrifuge/precise-proofs/blob/master/proofs/tree_test.go#L1351)\r\n\r\nFor more info on literal types and it's implementation see \r\nhttps://github.com/centrifuge/precise-proofs/issues/29","standard_bounties_id":2049,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":34,"github_org_name":"centrifuge","github_repo_name":"precise-proofs","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:33.907457Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1665&network=mainnet","increase":"/issue/increase?pk=1665&network=mainnet","accept":"/issue/accept?pk=1665&network=mainnet","cancel":"/issue/cancel?pk=1665&network=mainnet","payout":"/issue/payout?pk=1665&network=mainnet","contribute":"/issue/contribute?pk=1665&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1665&network=mainnet","social_contribution":"/issue/social_contribution?pk=1665&network=mainnet","invoice":"/issue/invoice?pk=1665&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Centrifuge","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/UniBitProject/wallet/20/2285","created_on":"2019-02-18T06:58:42.611642Z","modified_on":"2019-02-18T15:48:34.697226Z","title":"Apply an app walk-thru demonstration system","web3_created":"2018-12-24T06:34:25Z","value_in_token":"100.00","token_name":"CBTX","token_address":"0x886e38459D6D47553Ed810B2c0574D43ED6185c2","bounty_type":"Documentation","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/UniBitProject/wallet/issues/20","github_comments":0,"bounty_owner_address":"0x0e18d3d96a3e5334fa7f10ae6dc95203d28dc7ce","bounty_owner_email":"royhodge830@gmail.com","bounty_owner_github_username":"royhodge","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-27T06:34:25Z","activities":[],"keywords":"JavaScript, TypeScript, HTML, CSS","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.927942Z","avatar_url":"http://localhost:8000/dynamic/avatar/UniBitProject","value_true":"0.00","issue_description":"Apply an app walk-thru demonstration system, using the intro JS library\r\n2-3 hours guesstimated\r\n","network":"mainnet","org_name":"UniBitProject","pk":1864,"issue_description_text":"Apply an app walk-thru demonstration system, using the intro JS library\r\n2-3 hours guesstimated","standard_bounties_id":2285,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":20,"github_org_name":"UniBitProject","github_repo_name":"wallet","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:34.720191Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1864&network=mainnet","increase":"/issue/increase?pk=1864&network=mainnet","accept":"/issue/accept?pk=1864&network=mainnet","cancel":"/issue/cancel?pk=1864&network=mainnet","payout":"/issue/payout?pk=1864&network=mainnet","contribute":"/issue/contribute?pk=1864&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1864&network=mainnet","social_contribution":"/issue/social_contribution?pk=1864&network=mainnet","invoice":"/issue/invoice?pk=1864&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"UniBit Labs","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum-ts/TypeChain/131/2046","created_on":"2019-02-18T06:43:52.753582Z","modified_on":"2019-02-18T15:48:35.850845Z","title":"Support for truffle@5","web3_created":"2018-12-23T23:55:41Z","value_in_token":"200000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum-ts/TypeChain/issues/131","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-23T23:55:41Z","activities":[],"keywords":"TypeScript, JavaScript, Shell","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"200.00","value_in_usdt":"200.00","status":"open","now":"2019-02-18T16:03:19.939327Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum-ts","value_true":"200.00","issue_description":"Lately there have been some issues with latest versions of tools from the truffle suite.  \r\nSome update to the typings should happen sooner or later, or else TypeChain will become obsolete.  \r\n  \r\nMy first contact with Solidity ecosystem was just a few weeks ago and only with the *most current versions*, so I've managed to create a project that's cross-compatible internally.  \r\nWith a little bit of work I might have something that could serve as an update to the [truffle-typings](https://github.com/ethereum-ts/truffle-typings), but that's also still compatible with TypeChain and [existing example projects](https://github.com/ethereum-ts/truffle-typechain-example).  \r\nWould anyone be interested in that?  \r\nI already have something that works, I just need some _guidance_ in what is actually needed.  \r\n  \r\nHere is a link to my fork of the project:  [cymerrad/truffle-typings](https://github.com/cymerrad/truffle-typings)  \r\n  \r\nIssues I'm facing currently are, for example:\r\n1. What would be the preffered way of interacting with the package? Right now, in the example project mentioned eariler, types are being provided by tsconfig.json options:  \r\n` { \"typeRoots\": [\"./node_modules/@types\", \"./types\"], \"types\": [\"node\", \"truffle-contracts\"] } `  \r\nThis requires specifing *all* the types needed for the project, not just the truffle's.  \r\nIMHO, the dream-scenario would be just by importing `@types/truffle-contract` (otherwise the TS server will not know where to find the declarations outside of the typeRoots specified). However, could we still make it compatible with TypeChain?\r\n2. Should I provide all the properties existing on the objects and how deep should I go? From my experience with the truffle-contract project, I'd have to suggest *a lot* of changes to their project, as their usage of getters/setters is just pure insane.\r\n","network":"mainnet","org_name":"ethereum-ts","pk":1663,"issue_description_text":"Lately there have been some issues with latest versions of tools from the truffle suite.  \r\nSome update to the typings should happen sooner or later, or else TypeChain will become obsolete.  \r\n  \r\nMy first contact with Solidity ecosystem was just a few weeks ago and only with the *most current versions*, so I've managed to create a project that's cross-compatible internally.  \r\nWith a little bit of work I might have something that could serve as an update to the [truffle-typings](https://github.com/ethereum-ts/truffle-typings), but that's also still compatible with TypeChain and [existing example projects](https://github.com/ethereum-ts/truffle-typechain-example).  \r\nWould anyone be interested in that?  \r\nI already have something that works, I just need some _guidance_ in what is actually needed.  \r\n  \r\nHere is a link to my fork of the project:  [cymerrad/truffle-typings](https://github.com/cymerrad/truffle-typings)  \r\n  \r\nIssues I'm facing currently are, for example:\r\n1. What would be the preffered way of interacting with the package? Right now, in the example project mentioned eariler, types are being provided by tsconfig.json options:  \r\n` { \"typeRoots\": [\"./node_modules/@types\", \"./types\"], \"types\": [\"node\", \"truffle-contracts\"] } `  \r\nThis requires specifing *all* the types needed for the project, not just the truffle's.  \r\nIMHO, the dream-scenario would be just by importing `@types/truffle-contract` (otherwise the TS server will not know where to find the declarations outside of the typeRoots specified). However, could we still make it compatible with TypeChain?\r\n2. Should I provide all the properties existing on the objects and how deep should I go? From my experience with the truffle-contract project, I'd have to suggest *a lot* of changes to their project, as their usage of getters/setters is just pure insane.","standard_bounties_id":2046,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":131,"github_org_name":"ethereum-ts","github_repo_name":"TypeChain","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:35.870212Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1663&network=mainnet","increase":"/issue/increase?pk=1663&network=mainnet","accept":"/issue/accept?pk=1663&network=mainnet","cancel":"/issue/cancel?pk=1663&network=mainnet","payout":"/issue/payout?pk=1663&network=mainnet","contribute":"/issue/contribute?pk=1663&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1663&network=mainnet","social_contribution":"/issue/social_contribution?pk=1663&network=mainnet","invoice":"/issue/invoice?pk=1663&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/oceanprotocol/ocean-bounties/13/2032","created_on":"2019-02-18T06:42:56.406457Z","modified_on":"2019-02-18T15:48:36.615145Z","title":"Ocean Bounty: Smart Contract for Ocean DApp","web3_created":"2018-12-21T15:46:18Z","value_in_token":"2500000000000000000000.00","token_name":"PROCN","token_address":"0xf2aabdd898a0139195b2b5da7387d43a45ded254","bounty_type":"Feature","project_length":"Hours","experience_level":"","github_url":"https://github.com/oceanprotocol/ocean-bounties/issues/13","github_comments":0,"bounty_owner_address":"0x5a8302aa7046eb0f8d2e9e6fd3dda3416d5ecd8b","bounty_owner_email":"Anonymous","bounty_owner_github_username":"chalidbdb","bounty_owner_name":"Anonymous","fulfillments":[{"fulfiller_address":"0x69DAe3853D71fd09E47BfB3C37bB97586828afC9","fulfiller_email":"christopher.igbojekwe@gmail.com","fulfiller_github_username":"Christopher-I","fulfiller_name":"","fulfillment_id":1,"accepted":false,"profile":null,"created_on":"2019-02-18T06:42:57.445197Z","accepted_on":null,"fulfiller_github_url":""},{"fulfiller_address":"0x224698eB96e99e0D34B1B39Dc931a3c88c09107e","fulfiller_email":"mohammedehab93@gmail.com","fulfiller_github_username":"TheGooner93","fulfiller_name":"","fulfillment_id":0,"accepted":false,"profile":null,"created_on":"2019-02-18T06:42:57.438420Z","accepted_on":null,"fulfiller_github_url":"https://github.com/oceanprotocol/musicmap/pull/13"}],"interested":[],"is_open":true,"expires_date":"2019-01-20T15:46:18Z","activities":[],"keywords":"ethereum, smart contract, solidity, truffle, javascript, web3.js, Kovan, Rinkegy, musicmap, oceanprotocol ","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.946804Z","avatar_url":"http://localhost:8000/dynamic/avatar/oceanprotocol","value_true":"0.00","issue_description":"# Ocean Bounty : Smart Contract for Ocean DApp\r\nWe are working on a dApp using React (for frontend) and Express.js (for node.js server). We are using [material UI theme for React](https://material-ui.com/). We need your help to write the Ethereum smart contract that defines the rules and permissions of the application. We prefer to use **truffle** framework for this. \r\nWe already have some implementation of the app. See components diagram below.\r\n\r\n![mm-sketch_bounty2](https://user-images.githubusercontent.com/39778584/50293544-24b3ee80-0474-11e9-8348-b30362754f34.png)\r\n \r\n\r\n## How can you help?\r\n\r\nWrite a smart contract in Solidity that defines the incentives and rules for our musicmap app and that can be deployed on the Ethereum testnet (Kovan or Rinkeby). Our Dapp will eventually synchronize and perform operations on this smart contract using web3.js (but this web3.js integration is out-of-scope for this bounty. we will have seperate bounty for that later)\r\n\r\nIn this contract, the users of the network will need to be defined, as well as the entire incentive logic. \r\n\r\n[Link to Github Repo] (https://github.com/oceanprotocol/musicmap)\r\n\r\n**It is highly recommended to read the full business logic before starting [here](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part-iib.md).**\r\n\r\n\r\n## What needs to be done?\r\n\r\n### Logic & Mechanics (MOST IMP and MUST be implemented)\r\n\r\nThe following mechanics need to be implemented:\r\n* All new tracks will enter a “sandbox registry” with a score of zero. \r\n* For each song, users can vote either vouch or reject, which - after confirmation - will be irrevocably stored (the vote is locked) as part of each user's account.\r\n* Each track will display the current total number of votes (positive minus negative) = track rating.\r\n* For every similar vote (vouch or reject) after theirs, the user will get that vote as a credit point, but there will be two user scores: one for vouch votes and one for reject votes.\r\n* Each user will have a double total credit score, one for all vouch credit points and one for all reject credit points.\r\n* The genre score divided by the number of tracks equals the average track score.\r\n* Each user can have a maximum of 10 votes per day = UserDailyVoteCap.\r\n* Once a song goes below the BlacklistThreshold (default = -100), it gets blacklisted and removed from the registry.\r\n* Once a song goes above the WhitelistThreshold (default = +10), it will be placed in the whitelist (main) playlist.\r\n* Proposers and users who voted vouch get a penalty of 5 x average score when their song gets rejected (blacklisted).\r\n* Users who voted reject when the track gets whitelisted, get a penalty of the track rating minus WhitelistThreshold.\r\n* Governance Parameters and Default Values:\r\nWhitelistTreshold = 10\r\nBlacklistThreshold = -100\r\nUserDailyVoteCap = 10\r\nPunishmentMultiplier = 5\r\n\r\n### Solidity Smart contract template for above mechanics \r\n> **Note** : This is just a sample and for your reference and understanding. We don't expect the final code to have exactly similar structure. Most important is that this contract behaves according to the game mechanics and logic defined above.\r\n\r\n```javascript\r\n\r\n/************** variables **********************/\r\naverageScore = genreScore/totalTracks      //this value gets updated with new entries of tracks or with every user action\r\n\r\nmapping(hash => state) playlist;   // playlist mapping track hash to state {SANDBOX, WHITELIST}\r\n\r\n\r\n/**************  constants ********************/\r\nWhitelistThreshold = 10\r\nBlacklistThreshold = -100\r\n\r\n/**************** enums *****************/\r\nVote = {VOUCH, REJECT}\r\nState ={ SANDBOX, WHITELIST}\r\n\r\n/************* structs ***************/\r\nstruct tracks {\r\nhash        //this is a hash of all metadata (stored offchain in mongodb for that track)(also acts as track id)  \r\nscore                                //sum total of positive and negative votes for this track\r\nmapping(userId => Vote) userVotes            //total users who voted for this track and mapping of userId with Votes struct\r\n\r\n}\r\nstruct users {\r\nid                //public key of a user\r\nvouchCredits             //total credits earned by user when vouched for a track\r\nrejectCredits           //total credits earned by user when rejected a track\r\nmapping (hash => Vote) votes         //tracks this user has voted on and mapping of track hash with user’s vote {VOUCH, REJECT}\r\n\r\n}\r\n\r\n/****** functions *********/\r\n//this function vouches or rejects the given track based on user vote \r\nfunction VouchOrReject(trackHash, didVouch, userId){\r\n    //check if user has not already voted for this track\r\n        //update above mappings appropritely after calculating new state of the track in playlist and appropriate credits for this user and other users who voted for this track\r\n    _checkForRejection()\r\n    _distributeCredits(trackHash, didVouch, userId);\r\n    _updateAverageScore()\r\n        \r\n}\r\n//this function distributes credits appropriately based on game mechanics in above section\r\nfunction _distributeCredits(trackHash, didVouch, userId) {\r\n}\r\n//this function updates average score of this genre with every user action\r\nfunction _updateAverageScore(){}\r\n//this function checks if given track qualifies to be removed based on Rejection score\r\nfunction _checkForRejection(){}\r\n```\r\n\r\n### More information and documentation\r\n\r\nSee the full description of the curation mechanics here (only part II b is really within scope of this bounty):\r\n[Part I - Ingestion & General](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part_i.md)\r\n[Part IIb - Continuous Voting Model](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part-iib.md)\r\n[Part III - Conclusion & Rewards](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part_iii.md)\r\n\r\nThe PR should be created in the following repo: (new folder named \"contracts\" should be created)\r\nhttps://github.com/oceanprotocol/musicmap/tree/master/chain\r\n\r\n\r\n## We are happy when:\r\n- [ ] All the mechanics are written in Solidity code (with latest compiler) using truffle.js framework.\r\n- [ ] The smart contract can be deployed on an Ethereum testnet (rinkeby/ropsten)\r\n- [ ] Gas costs are not important but excessive actions should be avoided.\r\n- [ ] Tests are written and test coverage is above 80%\r\n- [ ] The code is merged into the master branch of the repo in the 'contracts' folder.\r\n- [ ] Write setup, deployment and usage instructions in README.md in 'contracts' folder\r\n\r\n\r\n## Seen this problem before?\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n## Questions & Reviews\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n## Things to know\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\nLastly, even if it is a contest bounty, we will reward all valuable contributions and efforts. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! :smiley:\r\n## Reward\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (price of Ocean Token during pre-launch was valued at 0.20 EUR/token. However, once the Ocean token is available on public exchanges, the Ocean token price will likely be different). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.\r\n","network":"mainnet","org_name":"oceanprotocol","pk":1653,"issue_description_text":"# Ocean Bounty : Smart Contract for Ocean DApp\r\nWe are working on a dApp using React (for frontend) and Express.js (for node.js server). We are using [material UI theme for React](https://material-ui.com/). We need your help to write the Ethereum smart contract that defines the rules and permissions of the application. We prefer to use **truffle** framework for this. \r\nWe already have some implementation of the app. See components diagram below.\r\n\r\n![mm-sketch_bounty2](https://user-images.githubusercontent.com/39778584/50293544-24b3ee80-0474-11e9-8348-b30362754f34.png)\r\n \r\n\r\n## How can you help?\r\n\r\nWrite a smart contract in Solidity that defines the incentives and rules for our musicmap app and that can be deployed on the Ethereum testnet (Kovan or Rinkeby). Our Dapp will eventually synchronize and perform operations on this smart contract using web3.js (but this web3.js integration is out-of-scope for this bounty. we will have seperate bounty for that later)\r\n\r\nIn this contract, the users of the network will need to be defined, as well as the entire incentive logic. \r\n\r\n[Link to Github Repo] (https://github.com/oceanprotocol/musicmap)\r\n\r\n**It is highly recommended to read the full business logic before starting [here](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part-iib.md).**\r\n\r\n\r\n## What needs to be done?\r\n\r\n### Logic & Mechanics (MOST IMP and MUST be implemented)\r\n\r\nThe following mechanics need to be implemented:\r\n* All new tracks will enter a “sandbox registry” with a score of zero. \r\n* For each song, users can vote either vouch or reject, which - after confirmation - will be irrevocably stored (the vote is locked) as part of each user's account.\r\n* Each track will display the current total number of votes (positive minus negative) = track rating.\r\n* For every similar vote (vouch or reject) after theirs, the user will get that vote as a credit point, but there will be two user scores: one for vouch votes and one for reject votes.\r\n* Each user will have a double total credit score, one for all vouch credit points and one for all reject credit points.\r\n* The genre score divided by the number of tracks equals the average track score.\r\n* Each user can have a maximum of 10 votes per day = UserDailyVoteCap.\r\n* Once a song goes below the BlacklistThreshold (default = -100), it gets blacklisted and removed from the registry.\r\n* Once a song goes above the WhitelistThreshold (default = +10), it will be placed in the whitelist (main) playlist.\r\n* Proposers and users who voted vouch get a penalty of 5 x average score when their song gets rejected (blacklisted).\r\n* Users who voted reject when the track gets whitelisted, get a penalty of the track rating minus WhitelistThreshold.\r\n* Governance Parameters and Default Values:\r\nWhitelistTreshold = 10\r\nBlacklistThreshold = -100\r\nUserDailyVoteCap = 10\r\nPunishmentMultiplier = 5\r\n\r\n### Solidity Smart contract template for above mechanics \r\n> **Note** : This is just a sample and for your reference and understanding. We don't expect the final code to have exactly similar structure. Most important is that this contract behaves according to the game mechanics and logic defined above.\r\n\r\n```javascript\r\n\r\n/************** variables **********************/\r\naverageScore = genreScore/totalTracks      //this value gets updated with new entries of tracks or with every user action\r\n\r\nmapping(hash => state) playlist;   // playlist mapping track hash to state {SANDBOX, WHITELIST}\r\n\r\n\r\n/**************  constants ********************/\r\nWhitelistThreshold = 10\r\nBlacklistThreshold = -100\r\n\r\n/**************** enums *****************/\r\nVote = {VOUCH, REJECT}\r\nState ={ SANDBOX, WHITELIST}\r\n\r\n/************* structs ***************/\r\nstruct tracks {\r\nhash        //this is a hash of all metadata (stored offchain in mongodb for that track)(also acts as track id)  \r\nscore                                //sum total of positive and negative votes for this track\r\nmapping(userId => Vote) userVotes            //total users who voted for this track and mapping of userId with Votes struct\r\n\r\n}\r\nstruct users {\r\nid                //public key of a user\r\nvouchCredits             //total credits earned by user when vouched for a track\r\nrejectCredits           //total credits earned by user when rejected a track\r\nmapping (hash => Vote) votes         //tracks this user has voted on and mapping of track hash with user’s vote {VOUCH, REJECT}\r\n\r\n}\r\n\r\n/****** functions *********/\r\n//this function vouches or rejects the given track based on user vote \r\nfunction VouchOrReject(trackHash, didVouch, userId){\r\n    //check if user has not already voted for this track\r\n        //update above mappings appropritely after calculating new state of the track in playlist and appropriate credits for this user and other users who voted for this track\r\n    _checkForRejection()\r\n    _distributeCredits(trackHash, didVouch, userId);\r\n    _updateAverageScore()\r\n        \r\n}\r\n//this function distributes credits appropriately based on game mechanics in above section\r\nfunction _distributeCredits(trackHash, didVouch, userId) {\r\n}\r\n//this function updates average score of this genre with every user action\r\nfunction _updateAverageScore(){}\r\n//this function checks if given track qualifies to be removed based on Rejection score\r\nfunction _checkForRejection(){}\r\n```\r\n\r\n### More information and documentation\r\n\r\nSee the full description of the curation mechanics here (only part II b is really within scope of this bounty):\r\n[Part I - Ingestion & General](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part_i.md)\r\n[Part IIb - Continuous Voting Model](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part-iib.md)\r\n[Part III - Conclusion & Rewards](https://github.com/oceanprotocol/musicmap/tree/master/specs/mechanics_part_iii.md)\r\n\r\nThe PR should be created in the following repo: (new folder named \"contracts\" should be created)\r\nhttps://github.com/oceanprotocol/musicmap/tree/master/chain\r\n\r\n\r\n## We are happy when:\r\n- [ ] All the mechanics are written in Solidity code (with latest compiler) using truffle.js framework.\r\n- [ ] The smart contract can be deployed on an Ethereum testnet (rinkeby/ropsten)\r\n- [ ] Gas costs are not important but excessive actions should be avoided.\r\n- [ ] Tests are written and test coverage is above 80%\r\n- [ ] The code is merged into the master branch of the repo in the 'contracts' folder.\r\n- [ ] Write setup, deployment and usage instructions in README.md in 'contracts' folder\r\n\r\n\r\n## Seen this problem before?\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n## Questions & Reviews\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n## Things to know\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\nLastly, even if it is a contest bounty, we will reward all valuable contributions and efforts. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! :smiley:\r\n## Reward\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (price of Ocean Token during pre-launch was valued at 0.20 EUR/token. However, once the Ocean token is available on public exchanges, the Ocean token price will likely be different). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.","standard_bounties_id":2032,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":13,"github_org_name":"oceanprotocol","github_repo_name":"ocean-bounties","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:36.633775Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":"2019-02-18T06:42:57.438420Z","fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1653&network=mainnet","increase":"/issue/increase?pk=1653&network=mainnet","accept":"/issue/accept?pk=1653&network=mainnet","cancel":"/issue/cancel?pk=1653&network=mainnet","payout":"/issue/payout?pk=1653&network=mainnet","contribute":"/issue/contribute?pk=1653&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1653&network=mainnet","social_contribution":"/issue/social_contribution?pk=1653&network=mainnet","invoice":"/issue/invoice?pk=1653&network=mainnet"},"project_type":"contest","permission_type":"approval","attached_job_description":"https://angel.co/oceanprotocol","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ocean Protocol Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gnosis/safe-browser-extension/92/2022","created_on":"2019-02-18T06:42:20.247123Z","modified_on":"2019-02-18T15:48:38.050893Z","title":"Test: fund this issue with gitcoin.co and the safe-browser-extension","web3_created":"2018-12-19T13:09:32Z","value_in_token":"1000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Documentation","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/gnosis/safe-browser-extension/issues/92","github_comments":0,"bounty_owner_address":"0x72eE53E890F6A0065dc6C35382F6528A474d8515","bounty_owner_email":"Anonymous","bounty_owner_github_username":"germartinez","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-20T13:09:32Z","activities":[],"keywords":"JavaScript, CSS, HTML","current_bounty":true,"value_in_eth":"1000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"0.00","value_in_usdt":"0.00","status":"open","now":"2019-02-18T16:03:19.954856Z","avatar_url":"http://localhost:8000/dynamic/avatar/gnosis","value_true":"0.00","issue_description":"Ignore this issue.\r\nThis is a test.","network":"mainnet","org_name":"gnosis","pk":1649,"issue_description_text":"Ignore this issue.\r\nThis is a test.","standard_bounties_id":2022,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":92,"github_org_name":"gnosis","github_repo_name":"safe-browser-extension","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:38.066510Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1649&network=mainnet","increase":"/issue/increase?pk=1649&network=mainnet","accept":"/issue/accept?pk=1649&network=mainnet","cancel":"/issue/cancel?pk=1649&network=mainnet","payout":"/issue/payout?pk=1649&network=mainnet","contribute":"/issue/contribute?pk=1649&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1649&network=mainnet","social_contribution":"/issue/social_contribution?pk=1649&network=mainnet","invoice":"/issue/invoice?pk=1649&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/status-im/status-react/7105/2019","created_on":"2019-02-18T06:42:08.739590Z","modified_on":"2019-02-18T15:48:40.290288Z","title":"Update extension input to support number range","web3_created":"2018-12-18T20:32:20Z","value_in_token":"80000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/status-im/status-react/issues/7105","github_comments":0,"bounty_owner_address":"0xa02378ca1c24767ecd776aafec02158a30dc01ac","bounty_owner_email":"statusgitcoin@gmail.com","bounty_owner_github_username":"StatusSceptre","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-18T20:32:20Z","activities":[],"keywords":"Clojure, Python, Objective-C, Shell, C++, Java, NSIS, JavaScript, CMake, Groovy, Dockerfile, Ruby, Makefile, QML, C, Batchfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"80.00","value_in_usdt":"80.00","status":"open","now":"2019-02-18T16:03:19.964791Z","avatar_url":"http://localhost:8000/dynamic/avatar/status-im","value_true":"80.00","issue_description":"\r\nAs a developer, I want a simple way to support input numerical ranges. When the value entered does not fit the range, show an error.\r\n\r\nDepends on #7104 \r\n\r\n### Description\r\n\r\n*Type*: Feature\r\n","network":"mainnet","org_name":"status-im","pk":1646,"issue_description_text":"As a developer, I want a simple way to support input numerical ranges. When the value entered does not fit the range, show an error.\r\n\r\nDepends on #7104 \r\n\r\n### Description\r\n\r\n*Type*: Feature","standard_bounties_id":2019,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":7105,"github_org_name":"status-im","github_repo_name":"status-react","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:40.308715Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1646&network=mainnet","increase":"/issue/increase?pk=1646&network=mainnet","accept":"/issue/accept?pk=1646&network=mainnet","cancel":"/issue/cancel?pk=1646&network=mainnet","payout":"/issue/payout?pk=1646&network=mainnet","contribute":"/issue/contribute?pk=1646&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1646&network=mainnet","social_contribution":"/issue/social_contribution?pk=1646&network=mainnet","invoice":"/issue/invoice?pk=1646&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/status-im/status-react/7075/2000","created_on":"2019-02-18T06:41:01.123871Z","modified_on":"2019-02-18T15:48:41.098519Z","title":"Expose ethereum logs details in an extension manipulable way","web3_created":"2018-12-14T16:55:12Z","value_in_token":"120000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/status-im/status-react/issues/7075","github_comments":0,"bounty_owner_address":"0xa02378ca1c24767ecd776aafec02158a30dc01ac","bounty_owner_email":"statusgitcoin@gmail.com","bounty_owner_github_username":"StatusSceptre","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-06-12T16:55:12Z","activities":[],"keywords":"Clojure, Python, Objective-C, Shell, C++, Java, NSIS, JavaScript, CMake, Groovy, Dockerfile, Ruby, Makefile, QML, C, Batchfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"120.00","value_in_usdt":"120.00","status":"open","now":"2019-02-18T16:03:19.973081Z","avatar_url":"http://localhost:8000/dynamic/avatar/status-im","value_true":"120.00","issue_description":"### User Story\r\n\r\nAs a developer, I want to have an easy access to both `data` and `logs` property from `logs` events in an easy to consume way. It could be exposed in a new `events` property.\r\n\r\n","network":"mainnet","org_name":"status-im","pk":1632,"issue_description_text":"### User Story\r\n\r\nAs a developer, I want to have an easy access to both `data` and `logs` property from `logs` events in an easy to consume way. It could be exposed in a new `events` property.","standard_bounties_id":2000,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":7075,"github_org_name":"status-im","github_repo_name":"status-react","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:41.112663Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1632&network=mainnet","increase":"/issue/increase?pk=1632&network=mainnet","accept":"/issue/accept?pk=1632&network=mainnet","cancel":"/issue/cancel?pk=1632&network=mainnet","payout":"/issue/payout?pk=1632&network=mainnet","contribute":"/issue/contribute?pk=1632&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1632&network=mainnet","social_contribution":"/issue/social_contribution?pk=1632&network=mainnet","invoice":"/issue/invoice?pk=1632&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.marketing/22/1983","created_on":"2019-02-18T06:39:59.047708Z","modified_on":"2019-02-18T15:48:41.954722Z","title":"Write blog tutorial for using Go as investor","web3_created":"2018-12-12T19:30:56Z","value_in_token":"8000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.marketing/issues/22","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T19:30:56Z","activities":[],"keywords":"writing, documentation, design, marketing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.980894Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe need a blog post written explaining how to use the Go platform as an investor. This should include the steps and explanation of each.\r\n\r\n## Requirements\r\n1. Must be easy to understand for people without a technical background\r\n2. limit the use of blockchain technology and vocabulary\r\n3. create a walkthrough of using the platform as an investor from start to finish including the required tools such as metamask and explain what metamask is.\r\n\r\n## Resources\r\n- https://go.mybit.io/app \r\n- https://files.mybit.io/files/\r\n\r\n## Expected Deliverables\r\n- Final script document in English in .doc or .docx format.\r\n- Distribution on your own personal medium and/or steemit account and promotion on your social channels\r\n\r\n## Additional Information\r\nThe creative process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1625,"issue_description_text":"## Introduction\r\nWe need a blog post written explaining how to use the Go platform as an investor. This should include the steps and explanation of each.\r\n\r\n## Requirements\r\n1. Must be easy to understand for people without a technical background\r\n2. limit the use of blockchain technology and vocabulary\r\n3. create a walkthrough of using the platform as an investor from start to finish including the required tools such as metamask and explain what metamask is.\r\n\r\n## Resources\r\n- https://go.mybit.io/app \r\n- https://files.mybit.io/files/\r\n\r\n## Expected Deliverables\r\n- Final script document in English in .doc or .docx format.\r\n- Distribution on your own personal medium and/or steemit account and promotion on your social channels\r\n\r\n## Additional Information\r\nThe creative process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1983,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":22,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.marketing","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:41.980764Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1625&network=mainnet","increase":"/issue/increase?pk=1625&network=mainnet","accept":"/issue/accept?pk=1625&network=mainnet","cancel":"/issue/cancel?pk=1625&network=mainnet","payout":"/issue/payout?pk=1625&network=mainnet","contribute":"/issue/contribute?pk=1625&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1625&network=mainnet","social_contribution":"/issue/social_contribution?pk=1625&network=mainnet","invoice":"/issue/invoice?pk=1625&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.marketing/33/1982","created_on":"2019-02-18T06:39:55.535838Z","modified_on":"2019-02-18T15:48:42.975356Z","title":"Animated explainer video of MyBit","web3_created":"2018-12-12T18:02:40Z","value_in_token":"80000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.marketing/issues/33","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T18:02:40Z","activities":[],"keywords":"writing, documentation, design, marketing, video","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.988905Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe need an animated video created which gives an analysis and explanation of the entire mybit project. It should be no longer than 75 seconds.\r\n\r\n## Requirements\r\n1. Must be easy to understand for people without a technical background\r\n2. limit the use of blockchain technology and vocabulary\r\n3. Include: MyBit Network, MyBit SDK, DDF, MyBit Go, MYDAX and vision of decentralisation and autonomy. \r\n\r\n## Resources\r\n- mybit.io\r\n- https://files.mybit.io/files/\r\n\r\n## Expected Deliverables\r\n- Final video in editable format and production format\r\n- Distribution on your own personal youtube and/or vimeo account and promotion on your social channels\r\n\r\n## Additional Information\r\nThe creative process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1624,"issue_description_text":"## Introduction\r\nWe need an animated video created which gives an analysis and explanation of the entire mybit project. It should be no longer than 75 seconds.\r\n\r\n## Requirements\r\n1. Must be easy to understand for people without a technical background\r\n2. limit the use of blockchain technology and vocabulary\r\n3. Include: MyBit Network, MyBit SDK, DDF, MyBit Go, MYDAX and vision of decentralisation and autonomy. \r\n\r\n## Resources\r\n- mybit.io\r\n- https://files.mybit.io/files/\r\n\r\n## Expected Deliverables\r\n- Final video in editable format and production format\r\n- Distribution on your own personal youtube and/or vimeo account and promotion on your social channels\r\n\r\n## Additional Information\r\nThe creative process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1982,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":33,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.marketing","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:42.993725Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1624&network=mainnet","increase":"/issue/increase?pk=1624&network=mainnet","accept":"/issue/accept?pk=1624&network=mainnet","cancel":"/issue/cancel?pk=1624&network=mainnet","payout":"/issue/payout?pk=1624&network=mainnet","contribute":"/issue/contribute?pk=1624&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1624&network=mainnet","social_contribution":"/issue/social_contribution?pk=1624&network=mainnet","invoice":"/issue/invoice?pk=1624&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/29/1980","created_on":"2019-02-18T06:39:49.073424Z","modified_on":"2019-02-18T15:48:45.015013Z","title":"Design Graphics for What is MyBit? Blog","web3_created":"2018-12-12T17:38:32Z","value_in_token":"5000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/29","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T17:38:32Z","activities":[],"keywords":"writing, documentation, design, marketing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:19.997311Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to add in some more visuals to the What is MyBit? (introduction) Blog.https://medium.com/mybit-dapp/introduction-a8275e6bcbec\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n```\r\n**Benefits of MyBit**\r\nMyBit offers many areas of value to the asset management industry. The benefits of MyBit include:\r\n\r\n* Lower cost to maintain ledgers\r\n* Lower cost to process transactions\r\n* Lower cost to send and receive capital\r\n* Lower cost to manage investments\r\n* Lower cost for redemptions and liquidations\r\n* True ownership. Investors hold full ownership of their capital and assets instead of a broker or fund.\r\n* Ability to transact without a broker by automatically establishing trust between transacting parties by proving ownership of assets and funds, and then completing the transaction via smart contracts.\r\n* Automated and real-time distributions of revenue\r\n* Public and auditable ledger (accounting) which also enables additional real-time data to be implemented\r\n* Ability to easily interact with Cryptographic assets (buy, sell, invest, trade, etc.)\r\n* Flexibility for existing funds to integrate into the MyBit Network or develop a new solution using the MyBit SDK.\r\n```\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n1. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n1. Upload finalised Blog with new graphics added in.\r\n1. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\nDisclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","network":"mainnet","org_name":"MyBitFoundation","pk":1622,"issue_description_text":"## Introduction\r\nWe want to add in some more visuals to the What is MyBit? (introduction) Blog.https://medium.com/mybit-dapp/introduction-a8275e6bcbec\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n```\r\n**Benefits of MyBit**\r\nMyBit offers many areas of value to the asset management industry. The benefits of MyBit include:\r\n\r\n* Lower cost to maintain ledgers\r\n* Lower cost to process transactions\r\n* Lower cost to send and receive capital\r\n* Lower cost to manage investments\r\n* Lower cost for redemptions and liquidations\r\n* True ownership. Investors hold full ownership of their capital and assets instead of a broker or fund.\r\n* Ability to transact without a broker by automatically establishing trust between transacting parties by proving ownership of assets and funds, and then completing the transaction via smart contracts.\r\n* Automated and real-time distributions of revenue\r\n* Public and auditable ledger (accounting) which also enables additional real-time data to be implemented\r\n* Ability to easily interact with Cryptographic assets (buy, sell, invest, trade, etc.)\r\n* Flexibility for existing funds to integrate into the MyBit Network or develop a new solution using the MyBit SDK.\r\n```\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n1. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n1. Upload finalised Blog with new graphics added in.\r\n1. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\nDisclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1980,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":29,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:45.032385Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1622&network=mainnet","increase":"/issue/increase?pk=1622&network=mainnet","accept":"/issue/accept?pk=1622&network=mainnet","cancel":"/issue/cancel?pk=1622&network=mainnet","payout":"/issue/payout?pk=1622&network=mainnet","contribute":"/issue/contribute?pk=1622&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1622&network=mainnet","social_contribution":"/issue/social_contribution?pk=1622&network=mainnet","invoice":"/issue/invoice?pk=1622&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/30/1979","created_on":"2019-02-18T06:39:45.912720Z","modified_on":"2019-02-18T15:48:46.435466Z","title":"Design Graphics for MyBit Token Blog","web3_created":"2018-12-12T17:25:56Z","value_in_token":"5000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/30","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T17:25:56Z","activities":[],"keywords":"writing, documentation, design, marketing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.005638Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to add in some more visuals to the MyBit Token Blog. https://medium.com/mybit-dapp/the-mybit-token-b79c4b1b8dbb\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n**Token Details**\r\nToken Name: **MyBit**\r\nSymbol: **MYB**\r\nDecimals: **18**\r\nTotal Supply: **180,000,000**\r\nCirculating Supply: **143,500,000** (after Phase 2 of token distribution)\r\nCoinMarketCap: https://coinmarketcap.com/currencies/mybit/\r\nSource Code: https://github.com/MyBitFoundation/MyBit-Token\r\nToken Logo: https://files.mybit.io/mybit-icon-28x28.png\r\nContract Address: 0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC\r\nToken Audit:\r\nhttps://github.com/MyBitFoundation/MyBitToken/blob/master/MyBit Audit Report - Solidified.pdf\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n1. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n1. Upload finalised Blog with new graphics added in.\r\n1. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","network":"mainnet","org_name":"MyBitFoundation","pk":1621,"issue_description_text":"## Introduction\r\nWe want to add in some more visuals to the MyBit Token Blog. https://medium.com/mybit-dapp/the-mybit-token-b79c4b1b8dbb\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n**Token Details**\r\nToken Name: **MyBit**\r\nSymbol: **MYB**\r\nDecimals: **18**\r\nTotal Supply: **180,000,000**\r\nCirculating Supply: **143,500,000** (after Phase 2 of token distribution)\r\nCoinMarketCap: https://coinmarketcap.com/currencies/mybit/\r\nSource Code: https://github.com/MyBitFoundation/MyBit-Token\r\nToken Logo: https://files.mybit.io/mybit-icon-28x28.png\r\nContract Address: 0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC\r\nToken Audit:\r\nhttps://github.com/MyBitFoundation/MyBitToken/blob/master/MyBit Audit Report - Solidified.pdf\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n1. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n1. Upload finalised Blog with new graphics added in.\r\n1. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1979,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":30,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:46.452890Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1621&network=mainnet","increase":"/issue/increase?pk=1621&network=mainnet","accept":"/issue/accept?pk=1621&network=mainnet","cancel":"/issue/cancel?pk=1621&network=mainnet","payout":"/issue/payout?pk=1621&network=mainnet","contribute":"/issue/contribute?pk=1621&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1621&network=mainnet","social_contribution":"/issue/social_contribution?pk=1621&network=mainnet","invoice":"/issue/invoice?pk=1621&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/oceanprotocol/ocean-bounties/11/1977","created_on":"2019-02-18T06:39:38.391097Z","modified_on":"2019-02-18T15:48:47.290776Z","title":"CLI for Ocean squid client libraries","web3_created":"2018-12-12T17:22:01Z","value_in_token":"12500000000000000000000.00","token_name":"PROCN","token_address":"0xf2aabdd898a0139195b2b5da7387d43a45ded254","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/oceanprotocol/ocean-bounties/issues/11","github_comments":0,"bounty_owner_address":"0x5a8302aa7046eb0f8d2e9e6fd3dda3416d5ecd8b","bounty_owner_email":"chalid@bigchaindb.com","bounty_owner_github_username":"chalidbdb","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-11T17:22:01Z","activities":[],"keywords":"CLI, java, python, javascript, oceanprotocol","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.013577Z","avatar_url":"http://localhost:8000/dynamic/avatar/oceanprotocol","value_true":"0.00","issue_description":"# CLI for Ocean squid client libraries\r\n\r\n\r\n## How can you help?\r\n\r\nWe want to implement a Command Line Interface for our client libraries “squid”. The latter are written in three languages [JavaScript](https://github.com/oceanprotocol/squid-js) (referred as squid-js); [Python](https://github.com/oceanprotocol/squid-py) (referred as squid-py); and [Java](https://github.com/oceanprotocol/squid-java) (referred as squid-java). In our architecture, the squid libraries allow users (publishers and consumers) to interact with the Ocean Protocol smart contracts and network. They include the methods (in different languages) to, for example, buy an asset, or publish it. Different languages have different uses: the JavaScript version will be mostly used in the front-end part of Ocean Protocol, when users will access the web pages. For now in our current version Trilobite, developers can interact with the libraries using [Tuna](https://github.com/oceanprotocol/tuna). Tuna is an example interface for our squid libraries.\r\nWe want to give developers the option to use a CLI to execute the different commands and methods. By building the CLI, you would help Ocean by expanding its functionalities while making it easier for developers to improve Ocean Protocol via the squid libraries. It should at least reproduce the capabilities of Tuna.\r\n\r\n\r\n## Assumptions\r\n\r\n* Familiarity with the Ocean Protocol architecture (you need to understand well how squid the libraries interacts with the different components). More information [here](https://github.com/oceanprotocol/).\r\n* You have used the current version (Trilobite) of Ocean Protocol and tried the different functionalities. This is will help you understand what the CLI should allow.\r\n* You have used/are using CLIs in your work/free time so you have knowledge about how to build one.\r\n\r\n\r\n## What needs to be done?\r\n\r\n* A complete CLI that developers can use to execute all the [commands](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md#squid-api-implementation-state) interacting with the squid libraries.\r\n* Any language (Python, JavaScript, Java) can be used, but it needs to be properly documented and tested (unit tests and integration tests).\r\n\r\n\r\n## We are very happy when\r\n\r\n* Users can easily understand how to operate the CLI (so solid documentation).\r\n* All the squid [commands](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md#squid-api-implementation-state) can be executed from the CLI (see list of commands https://github.com/oceanprotocol/squid-java/blob/develop/README.md). Users can publish, register, search, and consume assets, interact with the Secret Store (encrypt/decrypt), and interact with metadata. \r\n* Each CLI command should reproduce each squid method.\r\n* Unit/integration test coverage for the code is >=85%. \r\n\r\n\r\n## Seen this problem before?\r\n\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n\r\n\r\n## Questions & Reviews\r\n\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n\r\n\r\n## Things to know\r\n\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\n\r\n\r\n## Reward\r\n\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (currently Ocean Token is valued at 0.20 EUR). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.","network":"mainnet","org_name":"oceanprotocol","pk":1619,"issue_description_text":"# CLI for Ocean squid client libraries\r\n\r\n\r\n## How can you help?\r\n\r\nWe want to implement a Command Line Interface for our client libraries “squid”. The latter are written in three languages [JavaScript](https://github.com/oceanprotocol/squid-js) (referred as squid-js); [Python](https://github.com/oceanprotocol/squid-py) (referred as squid-py); and [Java](https://github.com/oceanprotocol/squid-java) (referred as squid-java). In our architecture, the squid libraries allow users (publishers and consumers) to interact with the Ocean Protocol smart contracts and network. They include the methods (in different languages) to, for example, buy an asset, or publish it. Different languages have different uses: the JavaScript version will be mostly used in the front-end part of Ocean Protocol, when users will access the web pages. For now in our current version Trilobite, developers can interact with the libraries using [Tuna](https://github.com/oceanprotocol/tuna). Tuna is an example interface for our squid libraries.\r\nWe want to give developers the option to use a CLI to execute the different commands and methods. By building the CLI, you would help Ocean by expanding its functionalities while making it easier for developers to improve Ocean Protocol via the squid libraries. It should at least reproduce the capabilities of Tuna.\r\n\r\n\r\n## Assumptions\r\n\r\n* Familiarity with the Ocean Protocol architecture (you need to understand well how squid the libraries interacts with the different components). More information [here](https://github.com/oceanprotocol/).\r\n* You have used the current version (Trilobite) of Ocean Protocol and tried the different functionalities. This is will help you understand what the CLI should allow.\r\n* You have used/are using CLIs in your work/free time so you have knowledge about how to build one.\r\n\r\n\r\n## What needs to be done?\r\n\r\n* A complete CLI that developers can use to execute all the [commands](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md#squid-api-implementation-state) interacting with the squid libraries.\r\n* Any language (Python, JavaScript, Java) can be used, but it needs to be properly documented and tested (unit tests and integration tests).\r\n\r\n\r\n## We are very happy when\r\n\r\n* Users can easily understand how to operate the CLI (so solid documentation).\r\n* All the squid [commands](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/architecture/squid.md#squid-api-implementation-state) can be executed from the CLI (see list of commands https://github.com/oceanprotocol/squid-java/blob/develop/README.md). Users can publish, register, search, and consume assets, interact with the Secret Store (encrypt/decrypt), and interact with metadata. \r\n* Each CLI command should reproduce each squid method.\r\n* Unit/integration test coverage for the code is >=85%. \r\n\r\n\r\n## Seen this problem before?\r\n\r\nAny help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.\r\n\r\n\r\n## Questions & Reviews\r\n\r\nPull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)\r\n\r\n\r\n## Things to know\r\n\r\nThe bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).\r\nWe'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.\r\nIn order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).\r\n\r\n\r\n## Reward\r\n\r\nOnce the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (currently Ocean Token is valued at 0.20 EUR). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.","standard_bounties_id":1977,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":11,"github_org_name":"oceanprotocol","github_repo_name":"ocean-bounties","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:47.310230Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1619&network=mainnet","increase":"/issue/increase?pk=1619&network=mainnet","accept":"/issue/accept?pk=1619&network=mainnet","cancel":"/issue/cancel?pk=1619&network=mainnet","payout":"/issue/payout?pk=1619&network=mainnet","contribute":"/issue/contribute?pk=1619&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1619&network=mainnet","social_contribution":"/issue/social_contribution?pk=1619&network=mainnet","invoice":"/issue/invoice?pk=1619&network=mainnet"},"project_type":"contest","permission_type":"approval","attached_job_description":"https://angel.co/oceanprotocol","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ocean Protocol Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/28/1973","created_on":"2019-02-18T06:39:21.099657Z","modified_on":"2019-02-18T15:48:48.300297Z","title":"Design Graphics for MyBit SDK Blog","web3_created":"2018-12-12T16:20:53Z","value_in_token":"5000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/28","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T16:20:53Z","activities":[],"keywords":"writing, documentation, design, marketing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.021828Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to add in some more visuals to the MyBit SDK Blog. https://medium.com/mybit-dapp/mybit-sdk-c5138657f66b\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n```\r\nTo create an asset on the blockchain:\r\n\r\n\r\n1. Import the MyBit Network object using npm\r\n\r\n* const Network = require(‘@mybit/network.js’);\r\n\r\n2. Add an Operator and let them accept ETH or ERC20\r\n\r\n\r\n* addOperator( account, name, owner ) returns ( bytes32 operatorID)\r\n* await Network.acceptEther(id, operatorAddress);\r\n\r\n3. Approve burner\r\n\r\n\r\n* await Network.approveBurn(operatorAddress);\r\n\r\n4. Create asset\r\n\r\n* var response = await Network.createAsset(), with parameters\r\n* assetURI: “ipfs/QmZfSNpHVz/”,\r\n* operatorID: operatorID,\r\n* fundingLength: 2629800,\r\n* amountToRaise: 49557286634011000832 //about $10,000\r\n* assetManagerPercent: 0,\r\n* assetManager: operatorAddress //operator is also broker\r\n```\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n3. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","network":"mainnet","org_name":"MyBitFoundation","pk":1615,"issue_description_text":"## Introduction\r\nWe want to add in some more visuals to the MyBit SDK Blog. https://medium.com/mybit-dapp/mybit-sdk-c5138657f66b\r\n\r\n## Requirements\r\n1. Turn this into a more appealing design.\r\n\r\n```\r\nTo create an asset on the blockchain:\r\n\r\n\r\n1. Import the MyBit Network object using npm\r\n\r\n* const Network = require(‘@mybit/network.js’);\r\n\r\n2. Add an Operator and let them accept ETH or ERC20\r\n\r\n\r\n* addOperator( account, name, owner ) returns ( bytes32 operatorID)\r\n* await Network.acceptEther(id, operatorAddress);\r\n\r\n3. Approve burner\r\n\r\n\r\n* await Network.approveBurn(operatorAddress);\r\n\r\n4. Create asset\r\n\r\n* var response = await Network.createAsset(), with parameters\r\n* assetURI: “ipfs/QmZfSNpHVz/”,\r\n* operatorID: operatorID,\r\n* fundingLength: 2629800,\r\n* amountToRaise: 49557286634011000832 //about $10,000\r\n* assetManagerPercent: 0,\r\n* assetManager: operatorAddress //operator is also broker\r\n```\r\n\r\n2. Add in 1-2 additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n3. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1973,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":28,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:48.322119Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1615&network=mainnet","increase":"/issue/increase?pk=1615&network=mainnet","accept":"/issue/accept?pk=1615&network=mainnet","cancel":"/issue/cancel?pk=1615&network=mainnet","payout":"/issue/payout?pk=1615&network=mainnet","contribute":"/issue/contribute?pk=1615&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1615&network=mainnet","social_contribution":"/issue/social_contribution?pk=1615&network=mainnet","invoice":"/issue/invoice?pk=1615&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/31/1971","created_on":"2019-02-18T06:39:10.809171Z","modified_on":"2019-02-18T15:48:49.998903Z","title":"Design Graphics for DAO Roadmap Blog","web3_created":"2018-12-12T14:29:10Z","value_in_token":"5000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Documentation","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/31","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-12T14:29:10Z","activities":[],"keywords":"writing, documentation, design, marketing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.029466Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to add in some more visuals to the DAO Roadmap Blog. https://medium.com/mybit-dapp/how-mybit-is-evolving-into-a-decentralised-autonomous-organisation-ff4b60fedbde\r\n\r\n## Requirements\r\n1. Add in a minimum of two (2) additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n2. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","network":"mainnet","org_name":"MyBitFoundation","pk":1614,"issue_description_text":"## Introduction\r\nWe want to add in some more visuals to the DAO Roadmap Blog. https://medium.com/mybit-dapp/how-mybit-is-evolving-into-a-decentralised-autonomous-organisation-ff4b60fedbde\r\n\r\n## Requirements\r\n1. Add in a minimum of two (2) additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n2. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n## Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1971,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":31,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:50.044613Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1614&network=mainnet","increase":"/issue/increase?pk=1614&network=mainnet","accept":"/issue/accept?pk=1614&network=mainnet","cancel":"/issue/cancel?pk=1614&network=mainnet","payout":"/issue/payout?pk=1614&network=mainnet","contribute":"/issue/contribute?pk=1614&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1614&network=mainnet","social_contribution":"/issue/social_contribution?pk=1614&network=mainnet","invoice":"/issue/invoice?pk=1614&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum-ts/TypeChain/109/1968","created_on":"2019-02-18T06:38:56.545890Z","modified_on":"2019-02-18T15:48:50.766868Z","title":"[Web3 1.0.0] Transactions (.send) should return void","web3_created":"2018-12-11T13:19:27Z","value_in_token":"100000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum-ts/TypeChain/issues/109","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-11T13:19:27Z","activities":[],"keywords":"TypeScript, JavaScript, Shell","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"100.00","value_in_usdt":"100.00","status":"open","now":"2019-02-18T16:03:20.049905Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum-ts","value_true":"100.00","issue_description":"`send` methods in web3 target have incorrect return types. \r\n\r\nHere is a failing test proving what's wrong: https://github.com/ethereum-ts/TypeChain/pull/129 Current return type is T (boolean in that case) where it should be a transaction object. \r\n\r\nThis could be an error in web3 typings, not necessary in Typechain but it will probably require some changes in typechain as well. ","network":"mainnet","org_name":"ethereum-ts","pk":1612,"issue_description_text":"`send` methods in web3 target have incorrect return types. \r\n\r\nHere is a failing test proving what's wrong: https://github.com/ethereum-ts/TypeChain/pull/129 Current return type is T (boolean in that case) where it should be a transaction object. \r\n\r\nThis could be an error in web3 typings, not necessary in Typechain but it will probably require some changes in typechain as well.","standard_bounties_id":1968,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":109,"github_org_name":"ethereum-ts","github_repo_name":"TypeChain","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:50.782207Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1612&network=mainnet","increase":"/issue/increase?pk=1612&network=mainnet","accept":"/issue/accept?pk=1612&network=mainnet","cancel":"/issue/cancel?pk=1612&network=mainnet","payout":"/issue/payout?pk=1612&network=mainnet","contribute":"/issue/contribute?pk=1612&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1612&network=mainnet","social_contribution":"/issue/social_contribution?pk=1612&network=mainnet","invoice":"/issue/invoice?pk=1612&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/For-Science/Crypto-For-Science/17/1952","created_on":"2019-02-18T06:38:03.643914Z","modified_on":"2019-02-18T15:48:51.945472Z","title":"New feature request: Email notification to Project Approvers, when a new campaign has been submitted","web3_created":"2018-12-09T18:41:15Z","value_in_token":"105000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/For-Science/Crypto-For-Science/issues/17","github_comments":0,"bounty_owner_address":"0x40215615943b641bcd8c39e74346b43759cf6071","bounty_owner_email":"laurentiu.andronache@trailung.ro","bounty_owner_github_username":"Laurentiu-Andronache","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-09T18:41:15Z","activities":[],"keywords":"JavaScript, HTML, CSS","current_bounty":true,"value_in_eth":"105000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"69.21","value_in_usdt":"69.21","status":"open","now":"2019-02-18T16:03:20.073603Z","avatar_url":"http://localhost:8000/dynamic/avatar/For-Science","value_true":"0.10","issue_description":"_If anyone wants to take development of this feature, just assign yourself here._\r\n\r\nNothing much to say, as it's clear from the title. Maybe a checkbox in their accounts where they could unsubscribe from this kind of notifications.","network":"mainnet","org_name":"For-Science","pk":1599,"issue_description_text":"_If anyone wants to take development of this feature, just assign yourself here._\r\n\r\nNothing much to say, as it's clear from the title. Maybe a checkbox in their accounts where they could unsubscribe from this kind of notifications.","standard_bounties_id":1952,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":17,"github_org_name":"For-Science","github_repo_name":"Crypto-For-Science","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:51.960839Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1599&network=mainnet","increase":"/issue/increase?pk=1599&network=mainnet","accept":"/issue/accept?pk=1599&network=mainnet","cancel":"/issue/cancel?pk=1599&network=mainnet","payout":"/issue/payout?pk=1599&network=mainnet","contribute":"/issue/contribute?pk=1599&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1599&network=mainnet","social_contribution":"/issue/social_contribution?pk=1599&network=mainnet","invoice":"/issue/invoice?pk=1599&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"ForSEH (For Science, Education and Healthcare)","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/transmission/transmission/47/1945","created_on":"2019-02-18T06:37:43.742116Z","modified_on":"2019-02-18T15:48:52.683702Z","title":"Support webrtc for webtorrent clients","web3_created":"2018-12-08T13:51:45Z","value_in_token":"600000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/transmission/transmission/issues/47","github_comments":0,"bounty_owner_address":"0x0fe8644ad1e50294525956d0e6689f4f5705ba73","bounty_owner_email":"jorropo.pgm@gmail.com","bounty_owner_github_username":"Jorropo","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T13:51:45Z","activities":[],"keywords":"C, C++, JavaScript, CSS, CMake, WebRTC","current_bounty":true,"value_in_eth":"600000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"415.26","value_in_usdt":"415.26","status":"open","now":"2019-02-18T16:03:20.099158Z","avatar_url":"http://localhost:8000/dynamic/avatar/transmission","value_true":"0.60","issue_description":"Hi, how difficult would it be to support clients connecting via webrtc?\r\n\r\nGitocin bounty details:\r\n\r\n> \r\n> For all people who will be working on from Gitcoin required things is (the % is what you will be paid) :\r\n> \r\n> Websocket tracker support [25%]\r\n> Exchange file beetween nodes [70%]\r\n> Use webtorrent if node is behind nat and can't use nat-pmp or upnp [5%]\r\n> The port for webtorrent doesn't need to be the same than regular torrent, (cause webtorrent use ICE)\r\n> ","network":"mainnet","org_name":"transmission","pk":1598,"issue_description_text":"Hi, how difficult would it be to support clients connecting via webrtc?\r\n\r\nGitocin bounty details:\r\n\r\n> \r\n> For all people who will be working on from Gitcoin required things is (the % is what you will be paid) :\r\n> \r\n> Websocket tracker support [25%]\r\n> Exchange file beetween nodes [70%]\r\n> Use webtorrent if node is behind nat and can't use nat-pmp or upnp [5%]\r\n> The port for webtorrent doesn't need to be the same than regular torrent, (cause webtorrent use ICE)\r\n>","standard_bounties_id":1945,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":47,"github_org_name":"transmission","github_repo_name":"transmission","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:52.703643Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1598&network=mainnet","increase":"/issue/increase?pk=1598&network=mainnet","accept":"/issue/accept?pk=1598&network=mainnet","cancel":"/issue/cancel?pk=1598&network=mainnet","payout":"/issue/payout?pk=1598&network=mainnet","contribute":"/issue/contribute?pk=1598&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1598&network=mainnet","social_contribution":"/issue/social_contribution?pk=1598&network=mainnet","invoice":"/issue/invoice?pk=1598&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethglobal/ethsingapore-bounties/4/1941","created_on":"2019-02-18T06:37:29.513239Z","modified_on":"2019-02-18T15:48:53.528307Z","title":"","web3_created":"2018-12-08T09:17:07Z","value_in_token":"50000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Other","project_length":"Days","experience_level":"Beginner","github_url":"https://github.com/ethglobal/ethsingapore-bounties/issues/4","github_comments":0,"bounty_owner_address":"0xf5e9d550c3c50364d630edb4753be404cd109121","bounty_owner_email":"","bounty_owner_github_username":"modong","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T09:17:07Z","activities":[],"keywords":"","current_bounty":true,"value_in_eth":"50000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"34.61","value_in_usdt":"34.61","status":"open","now":"2019-02-18T16:03:20.126736Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethglobal","value_true":"0.05","issue_description":"1000 prize, details coming soon!","network":"mainnet","org_name":"ethglobal","pk":1594,"issue_description_text":"1000 prize, details coming soon!","standard_bounties_id":1941,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":4,"github_org_name":"ethglobal","github_repo_name":"ethsingapore-bounties","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:53.549435Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1594&network=mainnet","increase":"/issue/increase?pk=1594&network=mainnet","accept":"/issue/accept?pk=1594&network=mainnet","cancel":"/issue/cancel?pk=1594&network=mainnet","payout":"/issue/payout?pk=1594&network=mainnet","contribute":"/issue/contribute?pk=1594&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1594&network=mainnet","social_contribution":"/issue/social_contribution?pk=1594&network=mainnet","invoice":"/issue/invoice?pk=1594&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Celer Network","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/web3.js/2080/1940","created_on":"2019-02-18T06:37:27.034854Z","modified_on":"2019-02-18T15:48:54.317992Z","title":"Answering issues with the label \"support\"","web3_created":"2018-12-08T08:15:22Z","value_in_token":"700000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Other","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum/web3.js/issues/2080","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[{"fulfiller_address":"0xC1C87Db54db59c3883700a700A10d6a3176a16A3","fulfiller_email":"chankruze@gmail.com","fulfiller_github_username":"chankruze","fulfiller_name":"","fulfillment_id":3,"accepted":false,"profile":null,"created_on":"2019-02-18T06:37:27.968173Z","accepted_on":null,"fulfiller_github_url":"https://github.com/ethereum/web3.js/issues/2080#issuecomment-450754423"},{"fulfiller_address":"0xf1a54014d7a4E3C5179579B050a0a0a036A158b0","fulfiller_email":"ja.m.es.quin.n.97@gmail.com","fulfiller_github_username":"Flash-Git","fulfiller_name":"","fulfillment_id":2,"accepted":false,"profile":null,"created_on":"2019-02-18T06:37:27.963294Z","accepted_on":null,"fulfiller_github_url":""},{"fulfiller_address":"0x0Ae1E349Ae4964eC6496D93CdAe4C58355072eD0","fulfiller_email":"bansall.shubham@gmail.com","fulfiller_github_username":"DragonSinMeliodas","fulfiller_name":"","fulfillment_id":1,"accepted":false,"profile":null,"created_on":"2019-02-18T06:37:27.956798Z","accepted_on":null,"fulfiller_github_url":""},{"fulfiller_address":"0x23bB837Fe8661f401F5a3462B108A120B45bA6bD","fulfiller_email":"vikasharry03@gmail.com","fulfiller_github_username":"vikaskyadav","fulfiller_name":"","fulfillment_id":0,"accepted":false,"profile":null,"created_on":"2019-02-18T06:37:27.950181Z","accepted_on":null,"fulfiller_github_url":"https://github.com/ethereum/web3.js/issues/2080#issuecomment-445467773"}],"interested":[],"is_open":true,"expires_date":"2019-01-07T08:15:22Z","activities":[],"keywords":"JavaScript, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"700.00","value_in_usdt":"700.00","status":"open","now":"2019-02-18T16:03:20.162664Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"700.00","issue_description":"This is a gitcoin bounty.\r\n\r\n#### ToDo:\r\n- [ ] Answer the question\r\n- [ ] Tag @nivida if you couldn't find a solution and describe it.\r\n- [ ] Tag @nivida if the documentation is wrong and add a URL to the docs and describe what's wrong.\r\n- [ ] Tag @nivida if the documentation should be improved and describe how.\r\n- [ ] Reference the issue here.","network":"mainnet","org_name":"ethereum","pk":1593,"issue_description_text":"This is a gitcoin bounty.\r\n\r\n#### ToDo:\r\n- [ ] Answer the question\r\n- [ ] Tag @nivida if you couldn't find a solution and describe it.\r\n- [ ] Tag @nivida if the documentation is wrong and add a URL to the docs and describe what's wrong.\r\n- [ ] Tag @nivida if the documentation should be improved and describe how.\r\n- [ ] Reference the issue here.","standard_bounties_id":1940,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":2080,"github_org_name":"ethereum","github_repo_name":"web3.js","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:54.333011Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":"2019-02-18T06:37:27.950181Z","fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1593&network=mainnet","increase":"/issue/increase?pk=1593&network=mainnet","accept":"/issue/accept?pk=1593&network=mainnet","cancel":"/issue/cancel?pk=1593&network=mainnet","payout":"/issue/payout?pk=1593&network=mainnet","contribute":"/issue/contribute?pk=1593&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1593&network=mainnet","social_contribution":"/issue/social_contribution?pk=1593&network=mainnet","invoice":"/issue/invoice?pk=1593&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/web3.js/2089/1938","created_on":"2019-02-18T06:37:16.870872Z","modified_on":"2019-02-18T15:48:55.193137Z","title":"Create live examples for the documentation examples.","web3_created":"2018-12-08T07:55:47Z","value_in_token":"250000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Documentation","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum/web3.js/issues/2089","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-08T07:55:47Z","activities":[],"keywords":"JavaScript, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"250.00","value_in_usdt":"250.00","status":"open","now":"2019-02-18T16:03:20.172049Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"250.00","issue_description":"## Documentation Feature Request:\r\nCurrently, many developers have trouble to understand how to interact with the ethereum blockchain over Web3.js/JSON-RPC. The documentation is not bad but if you just started to build a Dapp it's hard to do the first steps. \r\n\r\nThat's why I would like to have live examples with JsFiddle.\r\n\r\n#### ToDo's: \r\n- [ ] Check if ethereum-js really works otherwise have a look at eWASM.\r\n- [ ] Create simple example on JsFiddle.\r\n- [ ] Check if there is a nice way to provide these examples with readthedocs.\r\n- [ ] This examples could be placed in a separate repository. \r\n        (tag me and I will create a repository and give you access)\r\n\r\n##### Resources \r\nhttps://github.com/ethereumjs/browser-builds/tree/master/dist/ethereumjs-vm\r\nhttps://docs.jsfiddle.net/github-integration/untitled-1\r\n\r\n> Thanks Melonport for this idea ;-)","network":"mainnet","org_name":"ethereum","pk":1591,"issue_description_text":"## Documentation Feature Request:\r\nCurrently, many developers have trouble to understand how to interact with the ethereum blockchain over Web3.js/JSON-RPC. The documentation is not bad but if you just started to build a Dapp it's hard to do the first steps. \r\n\r\nThat's why I would like to have live examples with JsFiddle.\r\n\r\n#### ToDo's: \r\n- [ ] Check if ethereum-js really works otherwise have a look at eWASM.\r\n- [ ] Create simple example on JsFiddle.\r\n- [ ] Check if there is a nice way to provide these examples with readthedocs.\r\n- [ ] This examples could be placed in a separate repository. \r\n        (tag me and I will create a repository and give you access)\r\n\r\n##### Resources \r\nhttps://github.com/ethereumjs/browser-builds/tree/master/dist/ethereumjs-vm\r\nhttps://docs.jsfiddle.net/github-integration/untitled-1\r\n\r\n> Thanks Melonport for this idea ;-)","standard_bounties_id":1938,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":2089,"github_org_name":"ethereum","github_repo_name":"web3.js","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:55.209152Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1591&network=mainnet","increase":"/issue/increase?pk=1591&network=mainnet","accept":"/issue/accept?pk=1591&network=mainnet","cancel":"/issue/cancel?pk=1591&network=mainnet","payout":"/issue/payout?pk=1591&network=mainnet","contribute":"/issue/contribute?pk=1591&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1591&network=mainnet","social_contribution":"/issue/social_contribution?pk=1591&network=mainnet","invoice":"/issue/invoice?pk=1591&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3121/1937","created_on":"2019-02-18T06:37:13.523294Z","modified_on":"2019-02-18T15:48:56.777338Z","title":"Feature: Save Gitcoin Avatar to 3Box Profile","web3_created":"2018-12-08T07:46:28Z","value_in_token":"1000000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/gitcoinco/web/issues/3121","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-07T07:46:28Z","activities":[],"keywords":"JavaScript, Python, HTML, CSS, Shell, Makefile, Dockerfile, Smarty","current_bounty":true,"value_in_eth":"1000000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"692.10","value_in_usdt":"692.10","status":"open","now":"2019-02-18T16:03:20.181182Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"1.00","issue_description":"### User Story\r\n\r\n[comment]: # (As a <user type>, I want to <task> so that <goal>.)\r\nAs a user of Gitcoin who loves my Gitcoin Avatar, I would love to save my gitcoin avatar to my 3box profile so that I can use it in other dapps. It makes me look cool and digital.\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*: this is needed so I can use my gitcoin avatar throughout the web3 ecosystem via 3Box.\r\n\r\nThe Gitcoin Avatar builder allows users to create a fun avatar for their Gitcoin user account.\r\n\r\n3Box is building a distributed social profiles network for Ethereum. 3Box provides users with a [profiles dapp](https://3box.io) and developers with [distributed database infrastructure](https://github.com/3box/3box). 3Box dapp allows users to create a profile, log into dapps, store their information and more, while [3Box.js](https://github.com/3box/3box-js) enables your dapp to interact (set/get) with 3Box profiles.\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*: Feature\r\n\r\n### Current Behavior\r\n[comment]: # (Describe what actually happened.)\r\nRight now Gitcoin saves my avatar on their server, I also want to save a copy in my 3Box.\r\n\r\n### Expected Behavior\r\n[comment]: # (Describe what you expected to happen.)\r\nI would be over the moon to see this happen:\r\nAdd a button (or something) to the Gitcoin Avatar Builder page that allows the user to save their avatar file to 3Box. Might work something like this:\r\n1. Gitcoin app front-end would need to integrate 3Box.js\r\n2. User clicks \"Save to 3Box\" on the Avatar Builder page. Only users who have previously connected an ethereum account to their Gitcoin account will see that button.\r\n3. Gitcoin app presents the user with a 3Box consent message via the user's web3 browser signing interface (MetaMask, Status, or whatever), which authorizes the Gitcoin app to write and read from the user's 3Box. This is best supported by a modal that provides the user with a bit more information on why Gitcoin is asking them to do this. (But this is completely optional and def not required.)\r\n4. User approves the message.\r\n5. Gitcoin saves an entry to the user's public profile using box.public.set(gitcoin.avatar: 'IPFSHash').\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\nGitcoin avatar saves to 3Box profile. User can go to 3Box.io and see the file in their feed, and other developers can look up the public entry using getProfile(address) which is available via 3Box.js. The task would be finalized once a PR is submitted to the gitcoinco/web repo containing all of the code required to implement the solution described above.\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\nWould love to collab with the Gitcoin team on finding a solution here! hmu","network":"mainnet","org_name":"gitcoinco","pk":1590,"issue_description_text":"### User Story\r\n\r\n[comment]: # (As a , I want to  so that .)\r\nAs a user of Gitcoin who loves my Gitcoin Avatar, I would love to save my gitcoin avatar to my 3box profile so that I can use it in other dapps. It makes me look cool and digital.\r\n\r\n### Why Is this Needed\r\n\r\n[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)\r\n*Summary*: this is needed so I can use my gitcoin avatar throughout the web3 ecosystem via 3Box.\r\n\r\nThe Gitcoin Avatar builder allows users to create a fun avatar for their Gitcoin user account.\r\n\r\n3Box is building a distributed social profiles network for Ethereum. 3Box provides users with a [profiles dapp](https://3box.io) and developers with [distributed database infrastructure](https://github.com/3box/3box). 3Box dapp allows users to create a profile, log into dapps, store their information and more, while [3Box.js](https://github.com/3box/3box-js) enables your dapp to interact (set/get) with 3Box profiles.\r\n\r\n### Description\r\n\r\n[comment]: # (Feature or Bug? i.e Type: Bug)\r\n*Type*: Feature\r\n\r\n### Current Behavior\r\n[comment]: # (Describe what actually happened.)\r\nRight now Gitcoin saves my avatar on their server, I also want to save a copy in my 3Box.\r\n\r\n### Expected Behavior\r\n[comment]: # (Describe what you expected to happen.)\r\nI would be over the moon to see this happen:\r\nAdd a button (or something) to the Gitcoin Avatar Builder page that allows the user to save their avatar file to 3Box. Might work something like this:\r\n1. Gitcoin app front-end would need to integrate 3Box.js\r\n2. User clicks \"Save to 3Box\" on the Avatar Builder page. Only users who have previously connected an ethereum account to their Gitcoin account will see that button.\r\n3. Gitcoin app presents the user with a 3Box consent message via the user's web3 browser signing interface (MetaMask, Status, or whatever), which authorizes the Gitcoin app to write and read from the user's 3Box. This is best supported by a modal that provides the user with a bit more information on why Gitcoin is asking them to do this. (But this is completely optional and def not required.)\r\n4. User approves the message.\r\n5. Gitcoin saves an entry to the user's public profile using box.public.set(gitcoin.avatar: 'IPFSHash').\r\n\r\n### Definition of Done\r\n[comment]: # (Any other information that would be useful, bullets are helpful.)\r\nGitcoin avatar saves to 3Box profile. User can go to 3Box.io and see the file in their feed, and other developers can look up the public entry using getProfile(address) which is available via 3Box.js. The task would be finalized once a PR is submitted to the gitcoinco/web repo containing all of the code required to implement the solution described above.\r\n\r\n### Additional Information\r\n[comment]: # (Any other information that would be useful, content, screenshots, etc.)\r\nWould love to collab with the Gitcoin team on finding a solution here! hmu","standard_bounties_id":1937,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3121,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:56.794246Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1590&network=mainnet","increase":"/issue/increase?pk=1590&network=mainnet","accept":"/issue/accept?pk=1590&network=mainnet","cancel":"/issue/cancel?pk=1590&network=mainnet","payout":"/issue/payout?pk=1590&network=mainnet","contribute":"/issue/contribute?pk=1590&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1590&network=mainnet","social_contribution":"/issue/social_contribution?pk=1590&network=mainnet","invoice":"/issue/invoice?pk=1590&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/23/1935","created_on":"2019-02-18T06:37:05.170366Z","modified_on":"2019-02-18T15:48:57.782817Z","title":"Design Interface for IP Use Case","web3_created":"2018-12-08T07:24:09Z","value_in_token":"64000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/23","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T07:24:09Z","activities":[],"keywords":"design","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.189892Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nThe MyBit SDK makes it easy for anyone to register an asset and issue dividend tokens representing ownership. This is perfect for registering (digital) intellectual property such as a video. Through this model, anytime someone pays to view the video, revenue automatically is split to the holders of the dividend tokens aka IP owners.\r\n\r\nThe goal of this design is to create the UI for a dApp which makes it easy for anyone to register digital media on the Ethereum Blockchain and automatically issue dividend tokens to the owners.\r\n\r\n## Requirements\r\n1. Registering an asset requires the asset details and link or upload of the work.\r\n2. To issue dividend tokens the owners and their respective ETH addresses and ownership % must be indicated.\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for design and placement.\r\n2. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1588,"issue_description_text":"## Introduction\r\nThe MyBit SDK makes it easy for anyone to register an asset and issue dividend tokens representing ownership. This is perfect for registering (digital) intellectual property such as a video. Through this model, anytime someone pays to view the video, revenue automatically is split to the holders of the dividend tokens aka IP owners.\r\n\r\nThe goal of this design is to create the UI for a dApp which makes it easy for anyone to register digital media on the Ethereum Blockchain and automatically issue dividend tokens to the owners.\r\n\r\n## Requirements\r\n1. Registering an asset requires the asset details and link or upload of the work.\r\n2. To issue dividend tokens the owners and their respective ETH addresses and ownership % must be indicated.\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for design and placement.\r\n2. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1935,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":23,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:57.803158Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1588&network=mainnet","increase":"/issue/increase?pk=1588&network=mainnet","accept":"/issue/accept?pk=1588&network=mainnet","cancel":"/issue/cancel?pk=1588&network=mainnet","payout":"/issue/payout?pk=1588&network=mainnet","contribute":"/issue/contribute?pk=1588&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1588&network=mainnet","social_contribution":"/issue/social_contribution?pk=1588&network=mainnet","invoice":"/issue/invoice?pk=1588&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/20/1934","created_on":"2019-02-18T06:37:01.786513Z","modified_on":"2019-02-18T15:48:58.795120Z","title":"Design help center for DDF","web3_created":"2018-12-08T07:18:39Z","value_in_token":"49450000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/20","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T07:18:39Z","activities":[],"keywords":"design","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:20.197839Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to make it easy for people to understand how to use the MyBit DDF. This is why we need a help center page designed.\r\n\r\n## Requirements\r\n1. Help Center should be easily accessible from main page of DDF with button text \"Getting Started\"\r\n2. Help Center should include\r\n* quicklinks to guides for required tools such as Using Github, Metamask, OpenBounty, report bug\r\n* videos, blog posts, and other tutorials explaining MyBit Go. We can embed these most likely but will leave the decision up to the designer.\r\n* FAQ list similar to the knowledge base on go.mybit.io/app\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for design.\r\n2. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1587,"issue_description_text":"## Introduction\r\nWe want to make it easy for people to understand how to use the MyBit DDF. This is why we need a help center page designed.\r\n\r\n## Requirements\r\n1. Help Center should be easily accessible from main page of DDF with button text \"Getting Started\"\r\n2. Help Center should include\r\n* quicklinks to guides for required tools such as Using Github, Metamask, OpenBounty, report bug\r\n* videos, blog posts, and other tutorials explaining MyBit Go. We can embed these most likely but will leave the decision up to the designer.\r\n* FAQ list similar to the knowledge base on go.mybit.io/app\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for design.\r\n2. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional Information\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process. If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our [Gitter](https://gitter.im/Mybit-Foundation/DDF) channel.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1934,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":20,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:48:58.813808Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1587&network=mainnet","increase":"/issue/increase?pk=1587&network=mainnet","accept":"/issue/accept?pk=1587&network=mainnet","cancel":"/issue/cancel?pk=1587&network=mainnet","payout":"/issue/payout?pk=1587&network=mainnet","contribute":"/issue/contribute?pk=1587&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1587&network=mainnet","social_contribution":"/issue/social_contribution?pk=1587&network=mainnet","invoice":"/issue/invoice?pk=1587&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/mbeacom/test-repo/73/2014","created_on":"2019-02-18T06:41:50.237296Z","modified_on":"2019-02-18T06:41:50.237580Z","title":"git pull rebase and such","web3_created":"2018-12-08T06:12:31Z","value_in_token":"1000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/mbeacom/test-repo/issues/73","github_comments":0,"bounty_owner_address":"0x93d0def1d76b510e2a7a6d01cf18c54ec23f4253","bounty_owner_email":"mark.beacom@consensys.net","bounty_owner_github_username":"mbeacom","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T06:12:31Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:41:50.833729Z","profile":{"id":2,"handle":"mbeacom","github_url":"https://github.com/mbeacom","avatar_url":"http://localhost:8000/dynamic/avatar/mbeacom","url":"/profile/mbeacom"},"metadata":{"new_bounty":{"id":1642,"title":"git pull rebase and such","token_name":"ETH","value_in_eth":"1000000000000000","value_in_token":"1000000000000000","value_in_usdt_now":"0.0","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:41:50.243400+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1642,"tip":null}],"keywords":"Python","current_bounty":true,"value_in_eth":"1000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"0.00","value_in_usdt":"0.00","status":"open","now":"2019-02-18T16:03:20.205668Z","avatar_url":"http://localhost:8000/dynamic/avatar/mbeacom","value_true":"0.00","issue_description":"test test","network":"mainnet","org_name":"mbeacom","pk":1642,"issue_description_text":"test test","standard_bounties_id":2014,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":73,"github_org_name":"mbeacom","github_repo_name":"test-repo","idx_status":"open","token_value_time_peg":"2019-02-18T06:41:50.243400Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1642&network=mainnet","increase":"/issue/increase?pk=1642&network=mainnet","accept":"/issue/accept?pk=1642&network=mainnet","cancel":"/issue/cancel?pk=1642&network=mainnet","payout":"/issue/payout?pk=1642&network=mainnet","contribute":"/issue/contribute?pk=1642&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1642&network=mainnet","social_contribution":"/issue/social_contribution?pk=1642&network=mainnet","invoice":"/issue/invoice?pk=1642&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":null,"is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/mbeacom/test-repo/74/2013","created_on":"2019-02-18T06:41:47.399473Z","modified_on":"2019-02-18T06:41:47.399670Z","title":"Random bounty","web3_created":"2018-12-08T05:50:42Z","value_in_token":"1000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/mbeacom/test-repo/issues/74","github_comments":0,"bounty_owner_address":"0x93d0def1d76b510e2a7a6d01cf18c54ec23f4253","bounty_owner_email":"mark.beacom@consensys.net","bounty_owner_github_username":"mbeacom","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-08T05:50:42Z","activities":[{"activity_type":"new_bounty","created":"2019-02-18T06:41:47.958680Z","profile":{"id":2,"handle":"mbeacom","github_url":"https://github.com/mbeacom","avatar_url":"http://localhost:8000/dynamic/avatar/mbeacom","url":"/profile/mbeacom"},"metadata":{"new_bounty":{"id":1641,"title":"Random bounty","token_name":"ETH","value_in_eth":"1000000000000000","value_in_token":"1000000000000000","value_in_usdt_now":"0.0","token_value_in_usdt":"692.1","token_value_time_peg":"2019-02-18 06:41:47.406273+00:00"},"old_bounty":null,"fulfillment":null},"bounty":1641,"tip":null}],"keywords":"Python","current_bounty":true,"value_in_eth":"1000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"0.00","value_in_usdt":"0.00","status":"open","now":"2019-02-18T16:03:20.988194Z","avatar_url":"http://localhost:8000/dynamic/avatar/mbeacom","value_true":"0.00","issue_description":"Just a random bounty test","network":"mainnet","org_name":"mbeacom","pk":1641,"issue_description_text":"Just a random bounty test","standard_bounties_id":2013,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":74,"github_org_name":"mbeacom","github_repo_name":"test-repo","idx_status":"open","token_value_time_peg":"2019-02-18T06:41:47.406273Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1641&network=mainnet","increase":"/issue/increase?pk=1641&network=mainnet","accept":"/issue/accept?pk=1641&network=mainnet","cancel":"/issue/cancel?pk=1641&network=mainnet","payout":"/issue/payout?pk=1641&network=mainnet","contribute":"/issue/contribute?pk=1641&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1641&network=mainnet","social_contribution":"/issue/social_contribution?pk=1641&network=mainnet","invoice":"/issue/invoice?pk=1641&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":null,"is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit.design/32/1927","created_on":"2019-02-18T06:36:37.633121Z","modified_on":"2019-02-18T15:49:02.928999Z","title":"Design Graphics for Product Roadmap Blog","web3_created":"2018-12-07T15:17:53Z","value_in_token":"5000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Feature","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/MyBitFoundation/MyBit.design/issues/32","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-07T15:17:53Z","activities":[],"keywords":"design","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:21.707858Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe want to add in some more visuals to the Product Roadmap Blog. https://medium.com/mybit-dapp/a-look-at-mybits-past-present-and-future-plans-defbbdba2f67\r\n\r\n## Requirements\r\n1. Add in a minimum of two (2) additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit:\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n3. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information:\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process.\r\n\r\n## Additional Notes\r\nIf you have any questions, please feel free to ask in the thread or ping us at our Gitter channel - https://gitter.im/Mybit-Foundation/DDF\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1581,"issue_description_text":"## Introduction\r\nWe want to add in some more visuals to the Product Roadmap Blog. https://medium.com/mybit-dapp/a-look-at-mybits-past-present-and-future-plans-defbbdba2f67\r\n\r\n## Requirements\r\n1. Add in a minimum of two (2) additional graphics of your choice that appropriately describe a section of the blog.\r\n\r\n## Expected Deliverables\r\n1. Vector images of finalised designs. \r\n2. Images added to blog and shared (ready to publish)\r\n\r\n## To Submit:\r\n1. Upload graphics in separate files\r\n2. Upload finalised Blog with new graphics added in.\r\n3. Please submit a pull request with the final version once approved.\r\n\r\n## Additional Information:\r\nThe design process often involves multiple iterations. Therefore, please do not expect the task to be closed after the first version is submitted. We do understand the value of every contributors time, which is why we strive to make the task descriptions as detailed as possible. If you are unsure about a specific detail or have any questions please feel free to ask prior to starting or during the process.\r\n\r\n## Additional Notes\r\nIf you have any questions, please feel free to ask in the thread or ping us at our Gitter channel - https://gitter.im/Mybit-Foundation/DDF\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1927,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":32,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit.design","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:02.945712Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1581&network=mainnet","increase":"/issue/increase?pk=1581&network=mainnet","accept":"/issue/accept?pk=1581&network=mainnet","cancel":"/issue/cancel?pk=1581&network=mainnet","payout":"/issue/payout?pk=1581&network=mainnet","contribute":"/issue/contribute?pk=1581&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1581&network=mainnet","social_contribution":"/issue/social_contribution?pk=1581&network=mainnet","invoice":"/issue/invoice?pk=1581&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit-DDF.website/67/1926","created_on":"2019-02-18T06:36:34.825564Z","modified_on":"2019-02-18T15:49:05.637279Z","title":"Subscribe for notifications of new DDF tasks","web3_created":"2018-12-07T15:04:22Z","value_in_token":"25000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit-DDF.website/issues/67","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-07T15:04:22Z","activities":[],"keywords":"JavaScript, CSS, design, mailing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:21.714085Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe believe it is important for people to be notified when new tasks are added to the MyBit DDF. This is why we need an email submission feature with the ability to customise what you are alerted for implemented. Task #66 (https://github.com/MyBitFoundation/MyBit-DDF.website/issues/66) will also use this technology to expand notification capabilities on individual tasks.\r\n\r\n## Requirements\r\n1. Design and implement an email capture in a clear but not intrusive method on the current DDF design.\r\n2. Have the option to be notified for a specific category of a task such as Development, Design, or Marketing AND also be able to manage notifications for specific projects such as DDF, Go, MYDAX, SDK\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for email capture design and placement.\r\n2. Once approved, you will be supplied the mailing list API. 3. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1580,"issue_description_text":"## Introduction\r\nWe believe it is important for people to be notified when new tasks are added to the MyBit DDF. This is why we need an email submission feature with the ability to customise what you are alerted for implemented. Task #66 (https://github.com/MyBitFoundation/MyBit-DDF.website/issues/66) will also use this technology to expand notification capabilities on individual tasks.\r\n\r\n## Requirements\r\n1. Design and implement an email capture in a clear but not intrusive method on the current DDF design.\r\n2. Have the option to be notified for a specific category of a task such as Development, Design, or Marketing AND also be able to manage notifications for specific projects such as DDF, Go, MYDAX, SDK\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for email capture design and placement.\r\n2. Once approved, you will be supplied the mailing list API. 3. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1926,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":67,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit-DDF.website","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:05.658326Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1580&network=mainnet","increase":"/issue/increase?pk=1580&network=mainnet","accept":"/issue/accept?pk=1580&network=mainnet","cancel":"/issue/cancel?pk=1580&network=mainnet","payout":"/issue/payout?pk=1580&network=mainnet","contribute":"/issue/contribute?pk=1580&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1580&network=mainnet","social_contribution":"/issue/social_contribution?pk=1580&network=mainnet","invoice":"/issue/invoice?pk=1580&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MyBitFoundation/MyBit-DDF.website/66/1925","created_on":"2019-02-18T06:36:31.976236Z","modified_on":"2019-02-18T15:49:08.465798Z","title":"Alert contributors on PR submission","web3_created":"2018-12-07T14:58:19Z","value_in_token":"25000000000000000000000.00","token_name":"MYB","token_address":"0x5d60d8d7eF6d37E16EBABc324de3bE57f135e0BC","bounty_type":"Feature","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MyBitFoundation/MyBit-DDF.website/issues/66","github_comments":0,"bounty_owner_address":"0x8e73bdc0769a3d5b3103911400c0ee72daf3a71e","bounty_owner_email":"mybit.coordinator@gmail.com","bounty_owner_github_username":"mybit-coordinator","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-07T14:58:19Z","activities":[],"keywords":"JavaScript, CSS, design, mailing","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":null,"value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:21.721353Z","avatar_url":"http://localhost:8000/dynamic/avatar/MyBitFoundation","value_true":"0.00","issue_description":"## Introduction\r\nWe believe it is important for people to be notified about specific actions related to individual tasks. This is why we want to expand on the email notification functionality from task #67 (https://github.com/MyBitFoundation/MyBit-DDF.website/issues/67) to enable various notifications for specific tasks.\r\n\r\n## Requirements\r\n1. Design and implement a notification subscription button in a clear but not intrusive method on the current DDF design. This could be as simple as an icon on the specific task.\r\n2. When the icon is clicked on, a pop-up should display which allows people to choose which notifications they would like to receive (PR Submission, New Comment, Task Closed, or All). If you believe anything other than those 3 criteria should be eligible for notification, please propose via commenting on this task.\r\n3. This should be integrated with task #67 so once an email is input into that, it can be used for these notifications as well. There needs to be an error message that instructs to enter email there prior to being able to subscribe for notifications about individual tasks.\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for email capture design and placement.\r\n2. Once approved, you will be supplied the mailing list API (if applicable). \r\n3. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional notes\r\nAs always, if you think of a better implementation of this functionality, please propose by commenting on this task.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.\r\n\r\n","network":"mainnet","org_name":"MyBitFoundation","pk":1579,"issue_description_text":"## Introduction\r\nWe believe it is important for people to be notified about specific actions related to individual tasks. This is why we want to expand on the email notification functionality from task #67 (https://github.com/MyBitFoundation/MyBit-DDF.website/issues/67) to enable various notifications for specific tasks.\r\n\r\n## Requirements\r\n1. Design and implement a notification subscription button in a clear but not intrusive method on the current DDF design. This could be as simple as an icon on the specific task.\r\n2. When the icon is clicked on, a pop-up should display which allows people to choose which notifications they would like to receive (PR Submission, New Comment, Task Closed, or All). If you believe anything other than those 3 criteria should be eligible for notification, please propose via commenting on this task.\r\n3. This should be integrated with task #67 so once an email is input into that, it can be used for these notifications as well. There needs to be an error message that instructs to enter email there prior to being able to subscribe for notifications about individual tasks.\r\n\r\n## To Submit\r\n1. Comment on task with a testing URL to get approval for email capture design and placement.\r\n2. Once approved, you will be supplied the mailing list API (if applicable). \r\n3. Please submit a pull request with the final version including all functionality once complete.\r\n\r\n## Additional notes\r\nAs always, if you think of a better implementation of this functionality, please propose by commenting on this task.\r\n\r\n### Disclaimer\r\nAll work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.","standard_bounties_id":1925,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":66,"github_org_name":"MyBitFoundation","github_repo_name":"MyBit-DDF.website","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:08.480640Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1579&network=mainnet","increase":"/issue/increase?pk=1579&network=mainnet","accept":"/issue/accept?pk=1579&network=mainnet","cancel":"/issue/cancel?pk=1579&network=mainnet","payout":"/issue/payout?pk=1579&network=mainnet","contribute":"/issue/contribute?pk=1579&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1579&network=mainnet","social_contribution":"/issue/social_contribution?pk=1579&network=mainnet","invoice":"/issue/invoice?pk=1579&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MyBit AG","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/py_ecc/31/1924","created_on":"2019-02-18T06:36:28.137049Z","modified_on":"2019-02-18T15:49:10.378524Z","title":"Library refactor","web3_created":"2018-12-07T07:34:03Z","value_in_token":"250000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum/py_ecc/issues/31","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-07T07:34:03Z","activities":[],"keywords":"Python, Makefile, Shell","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"250.00","value_in_usdt":"250.00","status":"open","now":"2019-02-18T16:03:21.732698Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"250.00","issue_description":"By @Bhargavasomu from: https://github.com/ethereum/py_ecc/issues/24#issuecomment-442701351\r\n\r\nThe following things come to my mind.\r\n* The classes `FQ`, `FQP`, `FQ2` and `FQ12` need not be reinitialized every time as they are not dependent on the type of curve or extension. So probably we could have these created in `field_elements.py` and we could use them everywhere (`bn128`, `optimized_bn128`, `bls`, `optimized_bls`).\r\n* We could also have a general class `BaseCurve`, and then maybe every curve (`bn128_curve`, `optimized_bn128_curve`, ...) could inherit this and make the changes specific to the inherited class.\r\n* We should probably move the constants into a seperate file (`constants.py`)\r\n* We should also remove the assert statements which are not part of any function, but are part of the script in general, as shown\r\nhttps://github.com/ethereum/py_ecc/blob/067a40261ad39526f6aa8bd69def7d6982993d13/py_ecc/bn128/bn128_pairing.py#L74-L83\r\n* Also the type hinting should be further generalized wherever possible (in terms of removing redundant types; like `Optimized_FQPoint2D` could be replaced by `FQPoint2D`). Similary the type hinting should be carried out for the `bs12_381` and `optimized_bs12_381` submodules.\r\n\r\nAlso the only difference I see in all the curves is \r\n* Difference in the constants such as `b`, `b2`, `b12`, `G2`, `G12` ...\r\n* Difference in the `twist` function\r\n\r\n@vbuterin are my facts right or am I missing anything. \r\n@pipermerriam is the above design ok?","network":"mainnet","org_name":"ethereum","pk":1578,"issue_description_text":"By @Bhargavasomu from: https://github.com/ethereum/py_ecc/issues/24#issuecomment-442701351\r\n\r\nThe following things come to my mind.\r\n* The classes `FQ`, `FQP`, `FQ2` and `FQ12` need not be reinitialized every time as they are not dependent on the type of curve or extension. So probably we could have these created in `field_elements.py` and we could use them everywhere (`bn128`, `optimized_bn128`, `bls`, `optimized_bls`).\r\n* We could also have a general class `BaseCurve`, and then maybe every curve (`bn128_curve`, `optimized_bn128_curve`, ...) could inherit this and make the changes specific to the inherited class.\r\n* We should probably move the constants into a seperate file (`constants.py`)\r\n* We should also remove the assert statements which are not part of any function, but are part of the script in general, as shown\r\nhttps://github.com/ethereum/py_ecc/blob/067a40261ad39526f6aa8bd69def7d6982993d13/py_ecc/bn128/bn128_pairing.py#L74-L83\r\n* Also the type hinting should be further generalized wherever possible (in terms of removing redundant types; like `Optimized_FQPoint2D` could be replaced by `FQPoint2D`). Similary the type hinting should be carried out for the `bs12_381` and `optimized_bs12_381` submodules.\r\n\r\nAlso the only difference I see in all the curves is \r\n* Difference in the constants such as `b`, `b2`, `b12`, `G2`, `G12` ...\r\n* Difference in the `twist` function\r\n\r\n@vbuterin are my facts right or am I missing anything. \r\n@pipermerriam is the above design ok?","standard_bounties_id":1924,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":31,"github_org_name":"ethereum","github_repo_name":"py_ecc","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:10.395091Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1578&network=mainnet","increase":"/issue/increase?pk=1578&network=mainnet","accept":"/issue/accept?pk=1578&network=mainnet","cancel":"/issue/cancel?pk=1578&network=mainnet","payout":"/issue/payout?pk=1578&network=mainnet","contribute":"/issue/contribute?pk=1578&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1578&network=mainnet","social_contribution":"/issue/social_contribution?pk=1578&network=mainnet","invoice":"/issue/invoice?pk=1578&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/go-ethereum/18254/1920","created_on":"2019-02-18T06:36:15.856864Z","modified_on":"2019-02-18T15:49:11.969349Z","title":"Need to throw error when methods are called at future blocks","web3_created":"2018-12-06T22:17:02Z","value_in_token":"404000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Bug","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/ethereum/go-ethereum/issues/18254","github_comments":0,"bounty_owner_address":"0x0c54fccd2e384b4bb6f2e405bf5cbc15a017aafb","bounty_owner_email":"Anonymous","bounty_owner_github_username":"danfinlay","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-12-06T22:17:02Z","activities":[],"keywords":"Go","current_bounty":true,"value_in_eth":"404000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"276.84","value_in_usdt":"276.84","status":"open","now":"2019-02-18T16:03:21.741126Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"0.40","issue_description":"#### System information\r\n\r\nGeth version: 1.8.15 (Infura)\r\nOS & Version: Linux\r\nCommit hash : \r\n\r\n#### Expected behaviour\r\n\r\nGeth should throw an error when making a request on a future block.\r\n\r\n#### Actual behaviour\r\n\r\nMany types of request simply return `null` or `0x` when the `block` parameter is an integer for a future unknown block.\r\n\r\nThis is especially troublesome for clients that hit load-balanced geth clusters like Infura, where one request for latest block could return one number, and then suddenly requests at that block height could start returning `null` and `0x`, resulting in inconsistent client app state.\r\n\r\nIn short: This is the cause of many bugs in MetaMask and Dapps building on MetaMask, and probably other similar clients as well, and there is no way for us to detect or work around this issue without a fix in Geth.\r\n\r\n#### Steps to reproduce the behaviour\r\n\r\nThis bug can be reproduced with many methods that we're aware of, and probably many more are possible.\r\n\r\n`getStorageAt` of a known contract (`mkr`) on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"jsonrpc\":\"2.0\",\"id\":914762274,\"method\":\"eth_getStorageAt\",\"params\":[\"0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2\",\"0x0\",\"0x962124\"]}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":914762274,\"result\":\"0x\"}`, as if the contract were never published.\r\n\r\n`eth_getTransactionCount` of an account with some mined transactions, on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"id\":6972925150872393,\"jsonrpc\":\"2.0\",\"params\":[\"0xfdea65c8e26263f6d9a1b5de9555d2931a33b825\",\"0x885ac5\"],\"method\":\"eth_getTransactionCount\"}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":6972925150872393,\"result\":null}`, as if there were no error. At least this value can possibly be detected as invalid.\r\n\r\n`eth_getBalance` on an account with some ether, on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"id\":2366105135518150,\"jsonrpc\":\"2.0\",\"params\":[\"0xfdea65c8e26263f6d9a1b5de9555d2931a33b825\",\"0x885ab5\"],\"method\":\"eth_getBalance\"}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":2366105135518150,\"result\":null}`, as if there were no error. At least this value can possibly be detected as invalid.\r\n\r\nRelated to #3483.","network":"mainnet","org_name":"ethereum","pk":1576,"issue_description_text":"#### System information\r\n\r\nGeth version: 1.8.15 (Infura)\r\nOS & Version: Linux\r\nCommit hash : \r\n\r\n#### Expected behaviour\r\n\r\nGeth should throw an error when making a request on a future block.\r\n\r\n#### Actual behaviour\r\n\r\nMany types of request simply return `null` or `0x` when the `block` parameter is an integer for a future unknown block.\r\n\r\nThis is especially troublesome for clients that hit load-balanced geth clusters like Infura, where one request for latest block could return one number, and then suddenly requests at that block height could start returning `null` and `0x`, resulting in inconsistent client app state.\r\n\r\nIn short: This is the cause of many bugs in MetaMask and Dapps building on MetaMask, and probably other similar clients as well, and there is no way for us to detect or work around this issue without a fix in Geth.\r\n\r\n#### Steps to reproduce the behaviour\r\n\r\nThis bug can be reproduced with many methods that we're aware of, and probably many more are possible.\r\n\r\n`getStorageAt` of a known contract (`mkr`) on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"jsonrpc\":\"2.0\",\"id\":914762274,\"method\":\"eth_getStorageAt\",\"params\":[\"0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2\",\"0x0\",\"0x962124\"]}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":914762274,\"result\":\"0x\"}`, as if the contract were never published.\r\n\r\n`eth_getTransactionCount` of an account with some mined transactions, on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"id\":6972925150872393,\"jsonrpc\":\"2.0\",\"params\":[\"0xfdea65c8e26263f6d9a1b5de9555d2931a33b825\",\"0x885ac5\"],\"method\":\"eth_getTransactionCount\"}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":6972925150872393,\"result\":null}`, as if there were no error. At least this value can possibly be detected as invalid.\r\n\r\n`eth_getBalance` on an account with some ether, on a future block:\r\n```\r\ncurl 'https://mainnet.infura.io/' -H 'pragma: no-cache' -H 'origin: null' -H 'accept-encoding: gzip, deflate, br' -H 'accept-language: en,fr;q=0.9,en-US;q=0.8,es;q=0.7' -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36' -H 'content-type: application/json' -H 'accept: application/json' -H 'cache-control: no-cache' -H 'authority: mainnet.infura.io' --data-binary '{\"id\":2366105135518150,\"jsonrpc\":\"2.0\",\"params\":[\"0xfdea65c8e26263f6d9a1b5de9555d2931a33b825\",\"0x885ab5\"],\"method\":\"eth_getBalance\"}' --compressed\r\n```\r\n\r\nReturns `{\"jsonrpc\":\"2.0\",\"id\":2366105135518150,\"result\":null}`, as if there were no error. At least this value can possibly be detected as invalid.\r\n\r\nRelated to #3483.","standard_bounties_id":1920,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":18254,"github_org_name":"ethereum","github_repo_name":"go-ethereum","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:11.989844Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1576&network=mainnet","increase":"/issue/increase?pk=1576&network=mainnet","accept":"/issue/accept?pk=1576&network=mainnet","cancel":"/issue/cancel?pk=1576&network=mainnet","payout":"/issue/payout?pk=1576&network=mainnet","contribute":"/issue/contribute?pk=1576&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1576&network=mainnet","social_contribution":"/issue/social_contribution?pk=1576&network=mainnet","invoice":"/issue/invoice?pk=1576&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"MetaMask","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/VolcaTech/cryptoxmas.xyz/32/1914","created_on":"2019-02-18T06:35:55.563276Z","modified_on":"2019-02-18T15:49:13.620011Z","title":"[UX] Add Wallet Connect support / Enable user to pay via QR code","web3_created":"2018-12-06T00:41:39Z","value_in_token":"30000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Feature","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/VolcaTech/cryptoxmas.xyz/issues/32","github_comments":0,"bounty_owner_address":"0x224cf0b963c59b95623b3dd6ce07b4ce40f7b134","bounty_owner_email":"Anonymous","bounty_owner_github_username":"Kisgus","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-20T00:41:39Z","activities":[],"keywords":"JavaScript, CSS, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"30.00","value_in_usdt":"30.00","status":"open","now":"2019-02-18T16:03:21.748238Z","avatar_url":"http://localhost:8000/dynamic/avatar/VolcaTech","value_true":"30.00","issue_description":"# This is a ✨ [Cryptoxmas.xyz](https://cryptoxmas.xyz/) bounty✨\r\n**Every bounty DAI paid out will be matched as a donation to this** [Venezuelan Giveth Campaign](https://release.giveth.io/campaigns/5c05357a4a1382778fc07cef)\r\n\r\n## Problem\r\n\r\nThe user should be able to browse NFTs using a web2 browser. Then use his mobile wallet to pay or send a QR code / payment link to another user.\r\n\r\n## Proposed solutions\r\n\r\nWhich one would be less work?\r\n\r\n- Add Wallet Connect support.\r\n- Wallet Connect may be too much. We only need to show a QR code, with the amount of ETH to be paid for the NFT. And check for the transfer confirmation.\r\n\r\n## Prioritization\r\n\r\nIts nice UX, but not needed for the launch.\r\n\r\n## Dependency\r\n\r\nSolving this, does not make much sense, if the user cannot browse NFTs in web2. (https://github.com/VolcaTech/cryptoxmas.xyz/issues/31)","network":"mainnet","org_name":"VolcaTech","pk":1571,"issue_description_text":"# This is a ✨ [Cryptoxmas.xyz](https://cryptoxmas.xyz/) bounty✨\r\n**Every bounty DAI paid out will be matched as a donation to this** [Venezuelan Giveth Campaign](https://release.giveth.io/campaigns/5c05357a4a1382778fc07cef)\r\n\r\n## Problem\r\n\r\nThe user should be able to browse NFTs using a web2 browser. Then use his mobile wallet to pay or send a QR code / payment link to another user.\r\n\r\n## Proposed solutions\r\n\r\nWhich one would be less work?\r\n\r\n- Add Wallet Connect support.\r\n- Wallet Connect may be too much. We only need to show a QR code, with the amount of ETH to be paid for the NFT. And check for the transfer confirmation.\r\n\r\n## Prioritization\r\n\r\nIts nice UX, but not needed for the launch.\r\n\r\n## Dependency\r\n\r\nSolving this, does not make much sense, if the user cannot browse NFTs in web2. (https://github.com/VolcaTech/cryptoxmas.xyz/issues/31)","standard_bounties_id":1914,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":32,"github_org_name":"VolcaTech","github_repo_name":"cryptoxmas.xyz","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:13.637848Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1571&network=mainnet","increase":"/issue/increase?pk=1571&network=mainnet","accept":"/issue/accept?pk=1571&network=mainnet","cancel":"/issue/cancel?pk=1571&network=mainnet","payout":"/issue/payout?pk=1571&network=mainnet","contribute":"/issue/contribute?pk=1571&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1571&network=mainnet","social_contribution":"/issue/social_contribution?pk=1571&network=mainnet","invoice":"/issue/invoice?pk=1571&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"cryptoxmas.xyz","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/trailofbits/slither/39/1904","created_on":"2019-02-18T06:35:19.173099Z","modified_on":"2019-02-18T15:49:14.955409Z","title":"Add support for Vyper","web3_created":"2018-12-04T17:24:13Z","value_in_token":"9300000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Weeks","experience_level":"","github_url":"https://github.com/trailofbits/slither/issues/39","github_comments":0,"bounty_owner_address":"0x0ac29a22542aa9898370b0a358ab030950d92766","bounty_owner_email":"dan@trailofbits.com","bounty_owner_github_username":"dguido","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-04T17:24:13Z","activities":[],"keywords":"Python, Solidity, Shell, Dockerfile","current_bounty":true,"value_in_eth":"9300000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"6436.57","value_in_usdt":"6436.57","status":"open","now":"2019-02-18T16:03:21.754881Z","avatar_url":"http://localhost:8000/dynamic/avatar/trailofbits","value_true":"9.30","issue_description":"SlithIR is flexible enough that we should be able to support Vyper with few modifications. This will require investigating how Vyper produces their AST and providing for some translation into SlithIR. SlithIR may need modification in the process to support the unique features of Vyper's AST.","network":"mainnet","org_name":"trailofbits","pk":1563,"issue_description_text":"SlithIR is flexible enough that we should be able to support Vyper with few modifications. This will require investigating how Vyper produces their AST and providing for some translation into SlithIR. SlithIR may need modification in the process to support the unique features of Vyper's AST.","standard_bounties_id":1904,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":39,"github_org_name":"trailofbits","github_repo_name":"slither","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:14.973057Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1563&network=mainnet","increase":"/issue/increase?pk=1563&network=mainnet","accept":"/issue/accept?pk=1563&network=mainnet","cancel":"/issue/cancel?pk=1563&network=mainnet","payout":"/issue/payout?pk=1563&network=mainnet","contribute":"/issue/contribute?pk=1563&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1563&network=mainnet","social_contribution":"/issue/social_contribution?pk=1563&network=mainnet","invoice":"/issue/invoice?pk=1563&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Trail of Bits","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/web3.js/1446/1901","created_on":"2019-02-18T06:35:07.710796Z","modified_on":"2019-02-18T15:49:16.349337Z","title":"BatchRequest return promise","web3_created":"2018-12-04T16:50:20Z","value_in_token":"60000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/ethereum/web3.js/issues/1446","github_comments":0,"bounty_owner_address":"0xc92d76e01bd4e7ce25819c94fc6c3aea7b2cd155","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-01-03T16:50:20Z","activities":[],"keywords":"JavaScript, HTML","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"60.00","value_in_usdt":"60.00","status":"open","now":"2019-02-18T16:03:21.760685Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"60.00","issue_description":"Currently the `BatchRequest` object has an `execute` function. This function will execute the batch request (presumably in order, although the documentation does not say so). The script which calls `execute` does not learn that execution has occurred and therefore the process will hang because you cannot call `process.exit()`.\r\n\r\nReturning a promise would fix that.","network":"mainnet","org_name":"ethereum","pk":1560,"issue_description_text":"Currently the `BatchRequest` object has an `execute` function. This function will execute the batch request (presumably in order, although the documentation does not say so). The script which calls `execute` does not learn that execution has occurred and therefore the process will hang because you cannot call `process.exit()`.\r\n\r\nReturning a promise would fix that.","standard_bounties_id":1901,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":1446,"github_org_name":"ethereum","github_repo_name":"web3.js","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:16.368503Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1560&network=mainnet","increase":"/issue/increase?pk=1560&network=mainnet","accept":"/issue/accept?pk=1560&network=mainnet","cancel":"/issue/cancel?pk=1560&network=mainnet","payout":"/issue/payout?pk=1560&network=mainnet","contribute":"/issue/contribute?pk=1560&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1560&network=mainnet","social_contribution":"/issue/social_contribution?pk=1560&network=mainnet","invoice":"/issue/invoice?pk=1560&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/SocialDAO/ads/1/1892","created_on":"2019-02-18T06:34:37.090040Z","modified_on":"2019-02-18T15:49:17.060158Z","title":"Create Social Media Site/App With Self Serving Advertising That Accepts Cryptocurrency","web3_created":"2018-12-01T07:13:57Z","value_in_token":"8999999999999999.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Other","project_length":"Months","experience_level":"Advanced","github_url":"https://github.com/SocialDAO/ads/issues/1","github_comments":0,"bounty_owner_address":"0x10babc6cf07e4e1326bc1e7a2f2aefd37ac20350","bounty_owner_email":"michael@tenqido.org","bounty_owner_github_username":"michaelten","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2335-10-22T01:00:36Z","activities":[],"keywords":"website app android ios","current_bounty":true,"value_in_eth":"8999999999999999.00","token_value_in_usdt":"692.10","value_in_usdt_now":"6.92","value_in_usdt":"6.92","status":"open","now":"2019-02-18T16:03:21.766944Z","avatar_url":"http://localhost:8000/dynamic/avatar/SocialDAO","value_true":"0.01","issue_description":"Create a social media site and app with self serving advertising that accepts cryptocurrency. All software must be open source. \r\n\r\nThe platform will accept Bitcoin Cash and Ethereum for payment, and there will also be a way for members to pay a small monthly fee of cryptocurrency to not see ads. The creator of this can create a setting to accept more cryptocurrencies in addition to Bitcoin Cash and Ethereum; that would just be a bonus though, not a requirement to fulfill this bounty. \r\n\r\nConsider forking Honest.cash, Mastodon, WordPress, or MediaWiki. \r\n\r\nThis needs to be a website and a smartphone app (available on Android and iOS). \r\n\r\nThis bounty will likely only be filled once many individuals contribute to it, so as to motivate and attract the attention of perhaps a few solid teams.  \r\n\r\nFull specifications can be found at: https://tenqido.com/social-media\r\n\r\n","network":"mainnet","org_name":"SocialDAO","pk":1553,"issue_description_text":"Create a social media site and app with self serving advertising that accepts cryptocurrency. All software must be open source. \r\n\r\nThe platform will accept Bitcoin Cash and Ethereum for payment, and there will also be a way for members to pay a small monthly fee of cryptocurrency to not see ads. The creator of this can create a setting to accept more cryptocurrencies in addition to Bitcoin Cash and Ethereum; that would just be a bonus though, not a requirement to fulfill this bounty. \r\n\r\nConsider forking Honest.cash, Mastodon, WordPress, or MediaWiki. \r\n\r\nThis needs to be a website and a smartphone app (available on Android and iOS). \r\n\r\nThis bounty will likely only be filled once many individuals contribute to it, so as to motivate and attract the attention of perhaps a few solid teams.  \r\n\r\nFull specifications can be found at: https://tenqido.com/social-media","standard_bounties_id":1892,"web3_type":"bounties_network","can_submit_after_expiration_date":false,"github_issue_number":1,"github_org_name":"SocialDAO","github_repo_name":"ads","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:17.076303Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1553&network=mainnet","increase":"/issue/increase?pk=1553&network=mainnet","accept":"/issue/accept?pk=1553&network=mainnet","cancel":"/issue/cancel?pk=1553&network=mainnet","payout":"/issue/payout?pk=1553&network=mainnet","contribute":"/issue/contribute?pk=1553&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1553&network=mainnet","social_contribution":"/issue/social_contribution?pk=1553&network=mainnet","invoice":"/issue/invoice?pk=1553&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Tenqido DAO","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/gitcoinco/web/3041/1890","created_on":"2019-02-18T06:34:17.081430Z","modified_on":"2019-02-18T15:49:18.243284Z","title":"Improve the accessibility of Gitcoin.co","web3_created":"2018-12-01T00:22:32Z","value_in_token":"100000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Improvement","project_length":"Hours","experience_level":"Beginner","github_url":"https://github.com/gitcoinco/web/issues/3041","github_comments":0,"bounty_owner_address":"0x75bbc7d37d3bf975b527cf2e99b947d61a22ef95","bounty_owner_email":"Anonymous","bounty_owner_github_username":"kingjacob","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-03-01T00:22:32Z","activities":[],"keywords":"JavaScript, Python, HTML, CSS, Accessibility","current_bounty":true,"value_in_eth":"100000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"69.21","value_in_usdt":"69.21","status":"open","now":"2019-02-18T16:03:21.773713Z","avatar_url":"http://localhost:8000/dynamic/avatar/gitcoinco","value_true":"0.10","issue_description":"### Why Is this Needed\r\nTo allow people with disabilities to access the site.\r\n[https://www.w3.org/wiki/Accessibility_testing#The_importance_of_the_user_interface](https://www.w3.org/wiki/Accessibility_testing#The_importance_of_the_user_interface)\r\n\r\n### Current Behavior\r\n<img width=\"1278\" alt=\"screen shot 2018-11-30 at 3 57 02 pm\" src=\"https://user-images.githubusercontent.com/806312/49321101-53185c80-f4ba-11e8-95e2-d025a3cf88f2.png\">\r\n\r\n### Definition of Done\r\nA score of 100 after running the chrome tool audit.\r\n\r\n### Additional Information\r\nThe above will only capture that which can be audited automatically, so if anyone has a better checklist of ensuring a page is accesibile. Please share.\r\n","network":"mainnet","org_name":"gitcoinco","pk":1552,"issue_description_text":"### Why Is this Needed\r\nTo allow people with disabilities to access the site.\r\n[https://www.w3.org/wiki/Accessibility_testing#The_importance_of_the_user_interface](https://www.w3.org/wiki/Accessibility_testing#The_importance_of_the_user_interface)\r\n\r\n### Current Behavior\r\n\r\n\r\n### Definition of Done\r\nA score of 100 after running the chrome tool audit.\r\n\r\n### Additional Information\r\nThe above will only capture that which can be audited automatically, so if anyone has a better checklist of ensuring a page is accesibile. Please share.","standard_bounties_id":1890,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":3041,"github_org_name":"gitcoinco","github_repo_name":"web","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:18.265881Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1552&network=mainnet","increase":"/issue/increase?pk=1552&network=mainnet","accept":"/issue/accept?pk=1552&network=mainnet","cancel":"/issue/cancel?pk=1552&network=mainnet","payout":"/issue/payout?pk=1552&network=mainnet","contribute":"/issue/contribute?pk=1552&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1552&network=mainnet","social_contribution":"/issue/social_contribution?pk=1552&network=mainnet","invoice":"/issue/invoice?pk=1552&network=mainnet"},"project_type":"traditional","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"PrimeRadiant.Capital","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/MetaMask/metamask-extension/5724/1873","created_on":"2019-02-18T06:33:21.793702Z","modified_on":"2019-02-18T15:49:18.991099Z","title":"Security concern - IPFS ENS Resolving","web3_created":"2018-11-29T08:22:31Z","value_in_token":"300000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/MetaMask/metamask-extension/issues/5724","github_comments":0,"bounty_owner_address":"0x48a63097e1ac123b1f5a8bbffafa4afa8192fab0","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-29T08:22:31Z","activities":[],"keywords":"JavaScript, CSS, HTML, Shell, Dockerfile","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"300.00","value_in_usdt":"300.00","status":"open","now":"2019-02-18T16:03:21.779667Z","avatar_url":"http://localhost:8000/dynamic/avatar/MetaMask","value_true":"300.00","issue_description":"**Describe the issue**\r\n\r\nUsing ```gateway.ipfs.io``` when resolving ```ENS``` sites is dangerous. It allows all ```dapps``` to have access over eachothers cookies as well as over the local storage. Research should be done into how this could be mitigated in order to protect users. \r\n\r\nDepending on how the new metamask opt-in feature works, this may also be dangerous. If it is domain wide, all dapps called through their ```ENS``` name are automatically permitted to use metamask.\r\n\r\nCould this be done by potentially adding a custom host to a users ```hosts``` file that resolves all ```*.ens``` domains to a custom local server which then simply replaces content?\r\n\r\n**Potentially helpful examples**\r\n - https://github.com/cpacia/ens-chrome-extension\r\n - https://chrome.google.com/webstore/detail/peername/kkdihlopcnkjinfjhbeopjfmnfpcoaop?hl=en","network":"mainnet","org_name":"MetaMask","pk":1539,"issue_description_text":"**Describe the issue**\r\n\r\nUsing ```gateway.ipfs.io``` when resolving ```ENS``` sites is dangerous. It allows all ```dapps``` to have access over eachothers cookies as well as over the local storage. Research should be done into how this could be mitigated in order to protect users. \r\n\r\nDepending on how the new metamask opt-in feature works, this may also be dangerous. If it is domain wide, all dapps called through their ```ENS``` name are automatically permitted to use metamask.\r\n\r\nCould this be done by potentially adding a custom host to a users ```hosts``` file that resolves all ```*.ens``` domains to a custom local server which then simply replaces content?\r\n\r\n**Potentially helpful examples**\r\n - https://github.com/cpacia/ens-chrome-extension\r\n - https://chrome.google.com/webstore/detail/peername/kkdihlopcnkjinfjhbeopjfmnfpcoaop?hl=en","standard_bounties_id":1873,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":5724,"github_org_name":"MetaMask","github_repo_name":"metamask-extension","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:19.004071Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1539&network=mainnet","increase":"/issue/increase?pk=1539&network=mainnet","accept":"/issue/accept?pk=1539&network=mainnet","cancel":"/issue/cancel?pk=1539&network=mainnet","payout":"/issue/payout?pk=1539&network=mainnet","contribute":"/issue/contribute?pk=1539&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1539&network=mainnet","social_contribution":"/issue/social_contribution?pk=1539&network=mainnet","invoice":"/issue/invoice?pk=1539&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/hellobloom/core/35/1871","created_on":"2019-02-18T06:33:14.269859Z","modified_on":"2019-02-18T15:49:19.926034Z","title":"Review the Bloom Smart Contracts for bugs","web3_created":"2018-11-28T18:56:40Z","value_in_token":"3000000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Bug","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/hellobloom/core/issues/35","github_comments":0,"bounty_owner_address":"0xb864250ff5ea1779e4aaf04097d1d5a20da6c107","bounty_owner_email":"derek@bloom.co","bounty_owner_github_username":"dereksilva","bounty_owner_name":"Anonymous","fulfillments":[{"fulfiller_address":"0x08ac6d7ce02e7CFa050eECa4aFF73B862B6889bB","fulfiller_email":"sanketh.uppalapati@research.iiit.ac.in","fulfiller_github_username":"srisankethu","fulfiller_name":"","fulfillment_id":0,"accepted":false,"profile":null,"created_on":"2019-02-18T06:33:15.228450Z","accepted_on":null,"fulfiller_github_url":"https://github.com/hellobloom/core/issues/35#issuecomment-444059531"}],"interested":[],"is_open":true,"expires_date":"2019-02-26T18:56:40Z","activities":[],"keywords":"TypeScript, JavaScript, Shell, Docker, Bloom, Ethereum, Blockchain, Solidity","current_bounty":true,"value_in_eth":"3000000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"2076.31","value_in_usdt":"2076.31","status":"open","now":"2019-02-18T16:03:21.785366Z","avatar_url":"http://localhost:8000/dynamic/avatar/hellobloom","value_true":"3.00","issue_description":"Review the smart contracts and tests in this repository. Identify and propose a fix for a bug. Submissions will be reviewed by the Bloom team and rewards will be issued according to the severity. Here are some examples:\r\n\r\n- Public/external/internal/private `on` functions. Check to make sure anything public cannot be abused.\r\n- Proper modifiers to restrict access to certain functions, like `onlyDuringInitialization`.\r\n- Front-running attacks: can someone submit delegated transactions in a different order or use the same signature in different functions to have different effects?\r\n- Token escrow: can tokens ever be minted? Check the math for adjusting escrow balances.\r\n- Signature re-use: are all signatures burned after using them so they can't be replayed?\r\n- Test coverage: run the tests (./bin/test) and review the test cases; check for missing test scenarios.\r\n- Third-party party contracts like Ownable.sol, SafeMath, SafeERC20. Are they used appropriately?\r\n\r\nHere is our bug bounty payment rubric/guideline:\r\n![bloom-dev-bounty-rubric](https://user-images.githubusercontent.com/17386531/49157192-33800900-f2ed-11e8-8fad-5c400defbe3d.png)","network":"mainnet","org_name":"hellobloom","pk":1537,"issue_description_text":"Review the smart contracts and tests in this repository. Identify and propose a fix for a bug. Submissions will be reviewed by the Bloom team and rewards will be issued according to the severity. Here are some examples:\r\n\r\n- Public/external/internal/private `on` functions. Check to make sure anything public cannot be abused.\r\n- Proper modifiers to restrict access to certain functions, like `onlyDuringInitialization`.\r\n- Front-running attacks: can someone submit delegated transactions in a different order or use the same signature in different functions to have different effects?\r\n- Token escrow: can tokens ever be minted? Check the math for adjusting escrow balances.\r\n- Signature re-use: are all signatures burned after using them so they can't be replayed?\r\n- Test coverage: run the tests (./bin/test) and review the test cases; check for missing test scenarios.\r\n- Third-party party contracts like Ownable.sol, SafeMath, SafeERC20. Are they used appropriately?\r\n\r\nHere is our bug bounty payment rubric/guideline:\r\n![bloom-dev-bounty-rubric](https://user-images.githubusercontent.com/17386531/49157192-33800900-f2ed-11e8-8fad-5c400defbe3d.png)","standard_bounties_id":1871,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":35,"github_org_name":"hellobloom","github_repo_name":"core","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:19.947833Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":"2019-02-18T06:33:15.228450Z","fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1537&network=mainnet","increase":"/issue/increase?pk=1537&network=mainnet","accept":"/issue/accept?pk=1537&network=mainnet","cancel":"/issue/cancel?pk=1537&network=mainnet","payout":"/issue/payout?pk=1537&network=mainnet","contribute":"/issue/contribute?pk=1537&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1537&network=mainnet","social_contribution":"/issue/social_contribution?pk=1537&network=mainnet","invoice":"/issue/invoice?pk=1537&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Bloom Protocol","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/opengift-io/opengift.io/13/1867","created_on":"2019-02-18T06:33:01.116804Z","modified_on":"2019-02-18T15:49:20.683524Z","title":"Credits Online-Hackathon (01.12.2018 - 06.01.2019)","web3_created":"2018-11-28T10:29:39Z","value_in_token":"1000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Weeks","experience_level":"","github_url":"https://github.com/opengift-io/opengift.io/issues/13","github_comments":0,"bounty_owner_address":"0x3aa8311552a28b30c816f6577dbd83b777f6c008","bounty_owner_email":"slava.b@opengift.io","bounty_owner_github_username":"opengift-io","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-12T10:29:39Z","activities":[],"keywords":"hackathon, hackathons, credits, Java, Python","current_bounty":true,"value_in_eth":"1000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"0.00","value_in_usdt":"0.00","status":"open","now":"2019-02-18T16:03:21.790795Z","avatar_url":"http://localhost:8000/dynamic/avatar/opengift-io","value_true":"0.00","issue_description":"### We are glad to announce our new online hackathon conducted in collaboration with [Credits](https://credits.com). \r\nThe hackathon starts on December, 1.\r\n[Register now](https://opengift.io/credits-hackathon/)\r\n\r\nThe total prize pool of the competition is **USD 10,000** worth of Credits (CS) tokens according to the price of 6th January, 2019 (the tokens are traded on exchanges)..\r\n### Rewards will be distributed as follows:\r\n- 1st place - $5000\r\n- 2nd place - $3000\r\n- 3rd place - $2000\r\n\r\nAll interaction with participants and submissions are done through [our platform](https://opengift.io/credits-hackathon/).\r\n\r\nCompetence in Java programming language is a requirement for participation in hackathon because smart contract on Credits platform are written in Java. Web page or mobile application can be developed in almost any programming languages (ActionScript, C, C++, C#, Cappuccino, Cocoa, Delphi, Erlang, Golang, Haskell, Java, Node.js, Objective-C, OCaml, Perl, PHP, Python, Ruby) and connected to blockchain platform via API module with the help of Apache Thrift technology.\r\n\r\nMoreover, Credits is providing Technical Webinars to help further understand a platform you’ll be working with during the hackathon. Online sessions will be conducted via official [Twitch channel](https://www.twitch.tv/creditscom) and all videos will be uploaded on [Youtube channel](https://www.youtube.com/c/CreditsBlockchain).\r\n\r\n### Schedule of the webinars:\r\n- 15th November — “How to use Credits API”\r\n- 22nd November — “Development of smart contracts using Credits platform”\r\n- 29th November — “Development of decentralized applications using Credits platform”\r\n\r\n### Technical task requirements:\r\n- Make an open-sourced solution and publish it in a dedicated repository on [Credits Github](https://github.com/CREDITSCOM/CS-Third-party-Integrations-and-Solutions);\r\n- The final result needs to match the definition of a minimal viable product (MVP) -[https://en.wikipedia.org/wiki/Minimum_viable_product](https://en.wikipedia.org/wiki/Minimum_viable_product) ;\r\n- Final result of your development should interact with Credits blockchain — send transactions, deploy smart contracts and be connected with credits network;\r\n- You should use the latest version of our software. Probably, at the time of hackathon it will be Testnet 3.0 release. Information about version releases will be published in [Credits Technical chat](https://t.me/creditstechnical). [Link for download](https://developers.credits.com/en/Articles/11).\r\n\r\n### Development process\r\nThere are two main areas to focus on during the hackathon:\r\n- Development of decentralized applications various industries, including: Internet of Things, banking, logistics, insurance, payments, medicine, copyright protection, industrial and consumer goods. You can get some inspiration on the [Credits website](https://credits.com/) (tab ‘Use Cases’.)\r\n- Development of useful infrastructure services, which will be helpful for the Credits ecosystem, for example: a web wallet, a hardware wallet, a blockchain explorer, a decentralized exchange, various cross-chain and atomic swaps solutions, escrow, etc.\r\n\r\n### What needs to be done on GitHub\r\n- Create a fork of [Third party Integrations and Solutions](https://github.com/CREDITSCOM/CS-Third-party-Integrations-and-Solutions);\r\n- Create a branch in you forked repository (the branch name must match your project name);\r\n- Develop your project and put the source code in your forked repository. Please keep the deadlines in mind!\r\n- Put you project in a separate directory (the name must match the project name);\r\n- When the project is finished, create a pull request to merge your branch with the master branch;\r\n- After the pull request is confirmed, your project will be added to the Credits’ repository. If your project is not finished, but you make a pull request before the deadline, your project will be added to the repository.\r\n\r\n### Hackathon schedule\r\n\r\n- 1 step — **registration**. Deadline — 00:00 UTC, December, 9. All submissions are done through OpenGift platform. [Direct link for registration](https://opengift.io/credits-hackathon/).\r\n- 2 step — **concept creation**. Deadline — 00:00 UTC, December, 9. During this stage you should create a brief introduction of your future project. It must contain the following points — dApps/service name, estimated target audience, problems that can be solved, estimated MVP functionality, final release functionality. You can also add any information which helps to understand your concept deeper. This information should be presented in pdf, ppt or pptx format and uploaded to OpenGift website.\r\n- 3 step — **development process**. Deadline — 00:00 UTC, December, 30. By the end of this stage you should publish source code of your project in the dedicated Github repository and send a link to the developed website or mobile app via OpenGift. We will choose ten finalists at the end of 3rd round for participation in 4th round.\r\n- 4 step — **presentation**. Deadline — 00:00 UTC, January, 6, 2019. During this stage you should create a short video (5 minutes max) containing the information about your project: concept, process of interaction with users, key features and benefits. The presentation should be clear and understandable for listeners.\r\n\r\n### Judging criteria\r\nCredits developers team, the CTO — Evgeniy Butyaev and Deputy CTO — Konstantinos Sotiropulos, will be in charge of selecting winners. We will evaluate development according to criteria below\r\n- Meeting a target audience needs\r\n- Easiness of an implementation process and ability to solve problems of a target audience\r\n- Creativity and innovative approach will be a huge advantage\r\n- Opportunity for expansion and growth\r\n- Quality and clarity of the development code\r\n- UX/UI\r\n- Speed of interaction with users\r\n\r\n### Useful links\r\n**General links:**\r\n- [Credits Technical Discussion chat](https://t.me/creditstechnical) for questions and answers\r\n- [Credits Developers Portal](https://developers.credits.com/en) for all technical documentation\r\n- [Credits Youtube channel](https://www.youtube.com/channel/UC7kjX_jgauCqmf_a4fqLGOQ) for technical webinars\r\n\r\n**Links to Credits platform use cases:**\r\n- [Lending](https://credits.com/en/Home/case/1)\r\n- [Bond issuance](https://credits.com/en/Home/case/6)\r\n- [Stablecoin unit of account](https://credits.com/en/Home/case/7)\r\n- [Insurance — Payment of Compensation](https://credits.com/en/Home/Industries/78)\r\n- [Delayed Departure Insurance](https://credits.com/en/Home/Industries/75)\r\n- [Gambling](https://credits.com/en/Home/otras/5)\r\n- [Logistic sphere](https://credits.com/en/Home/otras/1)\r\n- [Goods origin](https://credits.com/en/Home/case/4)\r\n- [Copyright protection](https://credits.com/en/Home/case/5)\r\n- [Medicine](https://credits.com/en/Home/Industries/79)\r\n- [Loyalty programs](https://credits.com/en/Home/case/2)\r\n\r\n### We wish you good luck!\r\n\r\n","network":"mainnet","org_name":"opengift-io","pk":1534,"issue_description_text":"### We are glad to announce our new online hackathon conducted in collaboration with [Credits](https://credits.com). \r\nThe hackathon starts on December, 1.\r\n[Register now](https://opengift.io/credits-hackathon/)\r\n\r\nThe total prize pool of the competition is **USD 10,000** worth of Credits (CS) tokens according to the price of 6th January, 2019 (the tokens are traded on exchanges)..\r\n### Rewards will be distributed as follows:\r\n- 1st place - $5000\r\n- 2nd place - $3000\r\n- 3rd place - $2000\r\n\r\nAll interaction with participants and submissions are done through [our platform](https://opengift.io/credits-hackathon/).\r\n\r\nCompetence in Java programming language is a requirement for participation in hackathon because smart contract on Credits platform are written in Java. Web page or mobile application can be developed in almost any programming languages (ActionScript, C, C++, C#, Cappuccino, Cocoa, Delphi, Erlang, Golang, Haskell, Java, Node.js, Objective-C, OCaml, Perl, PHP, Python, Ruby) and connected to blockchain platform via API module with the help of Apache Thrift technology.\r\n\r\nMoreover, Credits is providing Technical Webinars to help further understand a platform you’ll be working with during the hackathon. Online sessions will be conducted via official [Twitch channel](https://www.twitch.tv/creditscom) and all videos will be uploaded on [Youtube channel](https://www.youtube.com/c/CreditsBlockchain).\r\n\r\n### Schedule of the webinars:\r\n- 15th November — “How to use Credits API”\r\n- 22nd November — “Development of smart contracts using Credits platform”\r\n- 29th November — “Development of decentralized applications using Credits platform”\r\n\r\n### Technical task requirements:\r\n- Make an open-sourced solution and publish it in a dedicated repository on [Credits Github](https://github.com/CREDITSCOM/CS-Third-party-Integrations-and-Solutions);\r\n- The final result needs to match the definition of a minimal viable product (MVP) -[https://en.wikipedia.org/wiki/Minimum_viable_product](https://en.wikipedia.org/wiki/Minimum_viable_product) ;\r\n- Final result of your development should interact with Credits blockchain — send transactions, deploy smart contracts and be connected with credits network;\r\n- You should use the latest version of our software. Probably, at the time of hackathon it will be Testnet 3.0 release. Information about version releases will be published in [Credits Technical chat](https://t.me/creditstechnical). [Link for download](https://developers.credits.com/en/Articles/11).\r\n\r\n### Development process\r\nThere are two main areas to focus on during the hackathon:\r\n- Development of decentralized applications various industries, including: Internet of Things, banking, logistics, insurance, payments, medicine, copyright protection, industrial and consumer goods. You can get some inspiration on the [Credits website](https://credits.com/) (tab ‘Use Cases’.)\r\n- Development of useful infrastructure services, which will be helpful for the Credits ecosystem, for example: a web wallet, a hardware wallet, a blockchain explorer, a decentralized exchange, various cross-chain and atomic swaps solutions, escrow, etc.\r\n\r\n### What needs to be done on GitHub\r\n- Create a fork of [Third party Integrations and Solutions](https://github.com/CREDITSCOM/CS-Third-party-Integrations-and-Solutions);\r\n- Create a branch in you forked repository (the branch name must match your project name);\r\n- Develop your project and put the source code in your forked repository. Please keep the deadlines in mind!\r\n- Put you project in a separate directory (the name must match the project name);\r\n- When the project is finished, create a pull request to merge your branch with the master branch;\r\n- After the pull request is confirmed, your project will be added to the Credits’ repository. If your project is not finished, but you make a pull request before the deadline, your project will be added to the repository.\r\n\r\n### Hackathon schedule\r\n\r\n- 1 step — **registration**. Deadline — 00:00 UTC, December, 9. All submissions are done through OpenGift platform. [Direct link for registration](https://opengift.io/credits-hackathon/).\r\n- 2 step — **concept creation**. Deadline — 00:00 UTC, December, 9. During this stage you should create a brief introduction of your future project. It must contain the following points — dApps/service name, estimated target audience, problems that can be solved, estimated MVP functionality, final release functionality. You can also add any information which helps to understand your concept deeper. This information should be presented in pdf, ppt or pptx format and uploaded to OpenGift website.\r\n- 3 step — **development process**. Deadline — 00:00 UTC, December, 30. By the end of this stage you should publish source code of your project in the dedicated Github repository and send a link to the developed website or mobile app via OpenGift. We will choose ten finalists at the end of 3rd round for participation in 4th round.\r\n- 4 step — **presentation**. Deadline — 00:00 UTC, January, 6, 2019. During this stage you should create a short video (5 minutes max) containing the information about your project: concept, process of interaction with users, key features and benefits. The presentation should be clear and understandable for listeners.\r\n\r\n### Judging criteria\r\nCredits developers team, the CTO — Evgeniy Butyaev and Deputy CTO — Konstantinos Sotiropulos, will be in charge of selecting winners. We will evaluate development according to criteria below\r\n- Meeting a target audience needs\r\n- Easiness of an implementation process and ability to solve problems of a target audience\r\n- Creativity and innovative approach will be a huge advantage\r\n- Opportunity for expansion and growth\r\n- Quality and clarity of the development code\r\n- UX/UI\r\n- Speed of interaction with users\r\n\r\n### Useful links\r\n**General links:**\r\n- [Credits Technical Discussion chat](https://t.me/creditstechnical) for questions and answers\r\n- [Credits Developers Portal](https://developers.credits.com/en) for all technical documentation\r\n- [Credits Youtube channel](https://www.youtube.com/channel/UC7kjX_jgauCqmf_a4fqLGOQ) for technical webinars\r\n\r\n**Links to Credits platform use cases:**\r\n- [Lending](https://credits.com/en/Home/case/1)\r\n- [Bond issuance](https://credits.com/en/Home/case/6)\r\n- [Stablecoin unit of account](https://credits.com/en/Home/case/7)\r\n- [Insurance — Payment of Compensation](https://credits.com/en/Home/Industries/78)\r\n- [Delayed Departure Insurance](https://credits.com/en/Home/Industries/75)\r\n- [Gambling](https://credits.com/en/Home/otras/5)\r\n- [Logistic sphere](https://credits.com/en/Home/otras/1)\r\n- [Goods origin](https://credits.com/en/Home/case/4)\r\n- [Copyright protection](https://credits.com/en/Home/case/5)\r\n- [Medicine](https://credits.com/en/Home/Industries/79)\r\n- [Loyalty programs](https://credits.com/en/Home/case/2)\r\n\r\n### We wish you good luck!","standard_bounties_id":1867,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":13,"github_org_name":"opengift-io","github_repo_name":"opengift.io","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:20.776976Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1534&network=mainnet","increase":"/issue/increase?pk=1534&network=mainnet","accept":"/issue/accept?pk=1534&network=mainnet","cancel":"/issue/cancel?pk=1534&network=mainnet","payout":"/issue/payout?pk=1534&network=mainnet","contribute":"/issue/contribute?pk=1534&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1534&network=mainnet","social_contribution":"/issue/social_contribution?pk=1534&network=mainnet","invoice":"/issue/invoice?pk=1534&network=mainnet"},"project_type":"contest","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Credits.com","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/leapdao/solEVM-enforcer/27/1866","created_on":"2019-02-18T06:32:57.638395Z","modified_on":"2019-02-18T15:49:21.634103Z","title":"Impossible to track a state(stack, memory, accounts) when JUMP backward","web3_created":"2018-11-28T10:14:20Z","value_in_token":"500000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Bug","project_length":"Hours","experience_level":"Advanced","github_url":"https://github.com/leapdao/solEVM-enforcer/issues/27","github_comments":0,"bounty_owner_address":"0x986d9bb496abd602ffbab9291a2621834f0f03a3","bounty_owner_email":"inditow@gmail.com","bounty_owner_github_username":"ggs134","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2019-02-26T10:14:20Z","activities":[],"keywords":"Solidity, JavaScript, Shell","current_bounty":true,"value_in_eth":"500000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"346.05","value_in_usdt":"346.05","status":"open","now":"2019-02-18T16:03:21.796934Z","avatar_url":"http://localhost:8000/dynamic/avatar/leapdao","value_true":"0.50","issue_description":"`JUMP` and `JUMPI` opcode work well but do not seem to work well under one exception. For example, if the current pc is 100(JUMP), JUMP works well with 150(JUMPDEST), but not with 50(JUMPDEST).\r\n\r\nI'm testing here.\r\n: https://github.com/Onther-Tech/solEVM/blob/run-erc20/test/ERC20.test.js\r\n\r\n_e.g._\r\n\r\n2047 has JUMP opcode so we expect to jump to 0x69c(1692).\r\n\r\n_pcCount 2047:_\r\n![image](https://user-images.githubusercontent.com/20399507/48993755-fb5cb700-f182-11e8-9090-ed76ffef3d8e.png)\r\n\r\n_pcCount 2048:_\r\n![image](https://user-images.githubusercontent.com/20399507/48993848-7e7e0d00-f183-11e8-8d0e-aa70f9031af8.png)\r\n\r\nWhen the pcCount is 2048, it should go to 0x69c(1692), but it does not go.\r\n\r\nIt's good to jump to a bigger pc(JUMPDEST) than current pc(JUMP), but it doesn't seem to work well when jumping to a smaller pc(JUMPDEST) than current pc(JUMP). Do you happen to know why?","network":"mainnet","org_name":"leapdao","pk":1533,"issue_description_text":"`JUMP` and `JUMPI` opcode work well but do not seem to work well under one exception. For example, if the current pc is 100(JUMP), JUMP works well with 150(JUMPDEST), but not with 50(JUMPDEST).\r\n\r\nI'm testing here.\r\n: https://github.com/Onther-Tech/solEVM/blob/run-erc20/test/ERC20.test.js\r\n\r\n_e.g._\r\n\r\n2047 has JUMP opcode so we expect to jump to 0x69c(1692).\r\n\r\n_pcCount 2047:_\r\n![image](https://user-images.githubusercontent.com/20399507/48993755-fb5cb700-f182-11e8-9090-ed76ffef3d8e.png)\r\n\r\n_pcCount 2048:_\r\n![image](https://user-images.githubusercontent.com/20399507/48993848-7e7e0d00-f183-11e8-8d0e-aa70f9031af8.png)\r\n\r\nWhen the pcCount is 2048, it should go to 0x69c(1692), but it does not go.\r\n\r\nIt's good to jump to a bigger pc(JUMPDEST) than current pc(JUMP), but it doesn't seem to work well when jumping to a smaller pc(JUMPDEST) than current pc(JUMP). Do you happen to know why?","standard_bounties_id":1866,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":27,"github_org_name":"leapdao","github_repo_name":"solEVM-enforcer","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:21.655645Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1533&network=mainnet","increase":"/issue/increase?pk=1533&network=mainnet","accept":"/issue/accept?pk=1533&network=mainnet","cancel":"/issue/cancel?pk=1533&network=mainnet","payout":"/issue/payout?pk=1533&network=mainnet","contribute":"/issue/contribute?pk=1533&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1533&network=mainnet","social_contribution":"/issue/social_contribution?pk=1533&network=mainnet","invoice":"/issue/invoice?pk=1533&network=mainnet"},"project_type":"cooperative","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"closed","is_issue_closed":true,"additional_funding_summary":{},"funding_organisation":"Onther Inc.","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/ethereum/remix-ide/596/1860","created_on":"2019-02-18T06:32:36.574253Z","modified_on":"2019-02-18T15:49:22.357723Z","title":"Show the balance of all deployed contracts ","web3_created":"2018-11-27T00:19:47Z","value_in_token":"50000000000000000000.00","token_name":"DAI","token_address":"0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359","bounty_type":"Improvement","project_length":"Days","experience_level":"Intermediate","github_url":"https://github.com/ethereum/remix-ide/issues/596","github_comments":0,"bounty_owner_address":"0x48a63097e1ac123b1f5a8bbffafa4afa8192fab0","bounty_owner_email":"scott@gitcoin.co","bounty_owner_github_username":"ceresstation","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-27T00:19:47Z","activities":[],"keywords":"JavaScript, HTML, Shell, CSS","current_bounty":true,"value_in_eth":null,"token_value_in_usdt":"1.00","value_in_usdt_now":"50.00","value_in_usdt":"50.00","status":"open","now":"2019-02-18T16:03:21.803322Z","avatar_url":"http://localhost:8000/dynamic/avatar/ethereum","value_true":"50.00","issue_description":"","network":"mainnet","org_name":"ethereum","pk":1528,"issue_description_text":"","standard_bounties_id":1860,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":596,"github_org_name":"ethereum","github_repo_name":"remix-ide","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:22.376715Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1528&network=mainnet","increase":"/issue/increase?pk=1528&network=mainnet","accept":"/issue/accept?pk=1528&network=mainnet","cancel":"/issue/cancel?pk=1528&network=mainnet","payout":"/issue/payout?pk=1528&network=mainnet","contribute":"/issue/contribute?pk=1528&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1528&network=mainnet","social_contribution":"/issue/social_contribution?pk=1528&network=mainnet","invoice":"/issue/invoice?pk=1528&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Ethereum Foundation","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/hellobloom/share-kit/28/1857","created_on":"2019-02-18T06:32:27.414235Z","modified_on":"2019-02-18T15:49:23.092475Z","title":"Complete the Share Kit Sign-In example","web3_created":"2018-11-26T19:34:40Z","value_in_token":"2013999999999999700.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Other","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/hellobloom/share-kit/issues/28","github_comments":0,"bounty_owner_address":"0xb864250ff5ea1779e4aaf04097d1d5a20da6c107","bounty_owner_email":"derek@bloom.co","bounty_owner_github_username":"dereksilva","bounty_owner_name":"Anonymous","fulfillments":[{"fulfiller_address":"0x23bB837Fe8661f401F5a3462B108A120B45bA6bD","fulfiller_email":"vikasharry03@gmail.com","fulfiller_github_username":"vikaskyadav","fulfiller_name":"","fulfillment_id":1,"accepted":false,"profile":null,"created_on":"2019-02-18T06:32:28.487508Z","accepted_on":null,"fulfiller_github_url":"https://github.com/vikaskyadav/bloom-login"},{"fulfiller_address":"0x2186F17f32b9bb57B5823E4b1C47Db32EB3B0674","fulfiller_email":"prabhu.v@gmail.com","fulfiller_github_username":"pvela","fulfiller_name":"","fulfillment_id":0,"accepted":false,"profile":null,"created_on":"2019-02-18T06:32:28.482867Z","accepted_on":null,"fulfiller_github_url":"https://github.com/pvela/bloomcheck"}],"interested":[],"is_open":true,"expires_date":"2019-02-24T19:34:40Z","activities":[],"keywords":"TypeScript, JavaScript, Shell, Dockerfile, Bloom, Ethereum, Blockchain, Solidity, API","current_bounty":true,"value_in_eth":"2013999999999999700.00","token_value_in_usdt":"692.10","value_in_usdt_now":"1391.13","value_in_usdt":"1391.13","status":"open","now":"2019-02-18T16:03:21.809040Z","avatar_url":"http://localhost:8000/dynamic/avatar/hellobloom","value_true":"2.01","issue_description":"Complete the tutorial in the share kit readme here: [Using Share-Kit for BloomID Sign-In](https://github.com/hellobloom/share-kit#using-share-kit-for-bloomid-sign-in).\r\n\r\nInclude sample code and screenshots! **Successful submissions will be award 2 ETH!**\r\n\r\nHere is our bug bounty payment rubric/guideline:\r\n![bloom-dev-bounty-rubric](https://user-images.githubusercontent.com/17386531/49157192-33800900-f2ed-11e8-8fad-5c400defbe3d.png)","network":"mainnet","org_name":"hellobloom","pk":1525,"issue_description_text":"Complete the tutorial in the share kit readme here: [Using Share-Kit for BloomID Sign-In](https://github.com/hellobloom/share-kit#using-share-kit-for-bloomid-sign-in).\r\n\r\nInclude sample code and screenshots! **Successful submissions will be award 2 ETH!**\r\n\r\nHere is our bug bounty payment rubric/guideline:\r\n![bloom-dev-bounty-rubric](https://user-images.githubusercontent.com/17386531/49157192-33800900-f2ed-11e8-8fad-5c400defbe3d.png)","standard_bounties_id":1857,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":28,"github_org_name":"hellobloom","github_repo_name":"share-kit","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:23.117644Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":"2019-02-18T06:32:28.482867Z","fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1525&network=mainnet","increase":"/issue/increase?pk=1525&network=mainnet","accept":"/issue/accept?pk=1525&network=mainnet","cancel":"/issue/cancel?pk=1525&network=mainnet","payout":"/issue/payout?pk=1525&network=mainnet","contribute":"/issue/contribute?pk=1525&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1525&network=mainnet","social_contribution":"/issue/social_contribution?pk=1525&network=mainnet","invoice":"/issue/invoice?pk=1525&network=mainnet"},"project_type":"cooperative","permission_type":"permissionless","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Bloom Protocol","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/aragon/aragon-monthly/284/1850","created_on":"2019-02-18T06:31:58.351599Z","modified_on":"2019-02-18T15:49:24.437007Z","title":"Issue 12: Freeform article or opinion piece on governance, DAOs or DACs","web3_created":"2018-11-26T18:24:26Z","value_in_token":"30000000000000000000.00","token_name":"ANT","token_address":"0x960b236a07cf122663c4303350609a66a7b288c0","bounty_type":"","project_length":"Unknown","experience_level":"","github_url":"https://github.com/aragon/aragon-monthly/issues/284","github_comments":0,"bounty_owner_address":"0xf83775c95a00612d4cac5053dd484ffa81bae0ad","bounty_owner_email":"kris@hotmail.be","bounty_owner_github_username":"krrisis","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-26T18:24:26Z","activities":[],"keywords":"decentralization, governance, dao, dac","current_bounty":true,"value_in_eth":"0.17","token_value_in_usdt":"3.86","value_in_usdt_now":null,"value_in_usdt":null,"status":"open","now":"2019-02-18T16:03:21.814658Z","avatar_url":"http://localhost:8000/dynamic/avatar/aragon","value_true":"30.00","issue_description":"# Request for content\r\n\r\n_Be sure to check out the [Guide for submitting a new Article](https://monthly.aragon.org/guides/guide_for_submitting_articles/) for submitting a new request_\r\n\r\n### Request type:\r\n_Article_ \r\n\r\n#### Content type:\r\n_Opinion Piece_ \r\n\r\n### Description of the requested content\r\nThoughtful, freeform article on the subject `governance`. You have the freedom to write an editorial piece of your choosing, this can be an opinion piece or a general article. Make sure it has a clear link to the power of decentralizing governance, this can be both in the form of DAOs (decentralized autonomous organizations) or a variation on this, such as Giveth's DACs (decentralized altruistic communities).\r\n\r\n**Article must be original content created for this purpose and not published anywhere before this**.\r\n\r\n> An opinion piece is an article that mainly reflects the author's opinion about the subject. Opinion pieces in the newspaper are often written by a subject-matter expert, a person with a unique perspective on an issue.\r\n\r\n### Additional information\r\n- Minimum 1500 words, maximum 2500 words\r\n- A bounty of 30 ANT will be added to this issue \r\n- if you see this issue is already being filled and you have good content, plz comment on the issue in github with your topic and if relevant we'll create an extra issue + gitcoin bounty! \r\n\r\n### Deadline\r\nBy the end of the month, in time for Aragon Monthly issue #12\r\n","network":"mainnet","org_name":"aragon","pk":1518,"issue_description_text":"# Request for content\r\n\r\n_Be sure to check out the [Guide for submitting a new Article](https://monthly.aragon.org/guides/guide_for_submitting_articles/) for submitting a new request_\r\n\r\n### Request type:\r\n_Article_ \r\n\r\n#### Content type:\r\n_Opinion Piece_ \r\n\r\n### Description of the requested content\r\nThoughtful, freeform article on the subject `governance`. You have the freedom to write an editorial piece of your choosing, this can be an opinion piece or a general article. Make sure it has a clear link to the power of decentralizing governance, this can be both in the form of DAOs (decentralized autonomous organizations) or a variation on this, such as Giveth's DACs (decentralized altruistic communities).\r\n\r\n**Article must be original content created for this purpose and not published anywhere before this**.\r\n\r\n> An opinion piece is an article that mainly reflects the author's opinion about the subject. Opinion pieces in the newspaper are often written by a subject-matter expert, a person with a unique perspective on an issue.\r\n\r\n### Additional information\r\n- Minimum 1500 words, maximum 2500 words\r\n- A bounty of 30 ANT will be added to this issue \r\n- if you see this issue is already being filled and you have good content, plz comment on the issue in github with your topic and if relevant we'll create an extra issue + gitcoin bounty! \r\n\r\n### Deadline\r\nBy the end of the month, in time for Aragon Monthly issue #12","standard_bounties_id":1850,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":284,"github_org_name":"aragon","github_repo_name":"aragon-monthly","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:24.458808Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1518&network=mainnet","increase":"/issue/increase?pk=1518&network=mainnet","accept":"/issue/accept?pk=1518&network=mainnet","cancel":"/issue/cancel?pk=1518&network=mainnet","payout":"/issue/payout?pk=1518&network=mainnet","contribute":"/issue/contribute?pk=1518&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1518&network=mainnet","social_contribution":"/issue/social_contribution?pk=1518&network=mainnet","invoice":"/issue/invoice?pk=1518&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Aragon DAC","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/unlock-protocol/unlock/526/1846","created_on":"2019-02-18T06:31:44.492168Z","modified_on":"2019-02-18T15:49:25.383161Z","title":"Dashboard Transaction Log Page","web3_created":"2018-11-26T17:12:50Z","value_in_token":"2001999999999999700.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"Feature","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/unlock-protocol/unlock/issues/526","github_comments":0,"bounty_owner_address":"0x33ab07df7f09e793ddd1e9a25b079989a557119a","bounty_owner_email":"julien@unlock-protocol.com","bounty_owner_github_username":"julien51","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-10T17:12:50Z","activities":[],"keywords":"JavaScript, Shell, Dockerfile","current_bounty":true,"value_in_eth":"2001999999999999700.00","token_value_in_usdt":"692.10","value_in_usdt_now":"1384.21","value_in_usdt":"1384.21","status":"open","now":"2019-02-18T16:03:21.819923Z","avatar_url":"http://localhost:8000/dynamic/avatar/unlock-protocol","value_true":"2.00","issue_description":"## Description\r\nA separate page that shows all actions and transactions – essentially a log. Currently accounted for are:\r\n- Creating a new Lock\r\n- Renaming a Lock\r\n- Lock/Key price change\r\n- Key purchases\r\n- Withdrawing funds\r\n- Downloading data\r\n\r\nAlso note the new Log Page icon in the header of the dashboard (see screenshot below).\r\n\r\nSpecs: https://zpl.io/2vNZKOn\r\nAssets: [log.svg](https://github.com/unlock-protocol/unlock/blob/master/unlock-app/src/static/images/svg/log.svg)\r\n\r\n## Screenshot\r\n![dashboard transaction log](https://user-images.githubusercontent.com/1377389/48371483-047d5c80-e68a-11e8-81d7-9f904fa59601.png)\r\n\r\n\r\n<img width=\"922\" alt=\"log icon\" src=\"https://user-images.githubusercontent.com/1377389/48367343-5e782500-e67e-11e8-9756-20cc25e98a23.png\">\r\n","network":"mainnet","org_name":"unlock-protocol","pk":1514,"issue_description_text":"## Description\r\nA separate page that shows all actions and transactions – essentially a log. Currently accounted for are:\r\n- Creating a new Lock\r\n- Renaming a Lock\r\n- Lock/Key price change\r\n- Key purchases\r\n- Withdrawing funds\r\n- Downloading data\r\n\r\nAlso note the new Log Page icon in the header of the dashboard (see screenshot below).\r\n\r\nSpecs: https://zpl.io/2vNZKOn\r\nAssets: [log.svg](https://github.com/unlock-protocol/unlock/blob/master/unlock-app/src/static/images/svg/log.svg)\r\n\r\n## Screenshot\r\n![dashboard transaction log](https://user-images.githubusercontent.com/1377389/48371483-047d5c80-e68a-11e8-81d7-9f904fa59601.png)","standard_bounties_id":1846,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":526,"github_org_name":"unlock-protocol","github_repo_name":"unlock","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:25.399145Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1514&network=mainnet","increase":"/issue/increase?pk=1514&network=mainnet","accept":"/issue/accept?pk=1514&network=mainnet","cancel":"/issue/cancel?pk=1514&network=mainnet","payout":"/issue/payout?pk=1514&network=mainnet","contribute":"/issue/contribute?pk=1514&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1514&network=mainnet","social_contribution":"/issue/social_contribution?pk=1514&network=mainnet","invoice":"/issue/invoice?pk=1514&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"https://unlock-protocol.com/jobs","needs_review":[],"github_issue_state":"open","is_issue_closed":false,"additional_funding_summary":{},"funding_organisation":"Unlock Inc","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null},{"url":"http://localhost:8000/issue/unlock-protocol/unlock/138/1844","created_on":"2019-02-18T06:31:37.400232Z","modified_on":"2019-02-18T15:49:27.098796Z","title":"Allowing Lock owners to update the price of keys","web3_created":"2018-11-26T16:30:03Z","value_in_token":"1500000000000000000.00","token_name":"ETH","token_address":"0x0000000000000000000000000000000000000000","bounty_type":"","project_length":"Hours","experience_level":"Intermediate","github_url":"https://github.com/unlock-protocol/unlock/issues/138","github_comments":0,"bounty_owner_address":"0x33ab07df7f09e793ddd1e9a25b079989a557119a","bounty_owner_email":"Anonymous","bounty_owner_github_username":"julien51","bounty_owner_name":"Anonymous","fulfillments":[],"interested":[],"is_open":true,"expires_date":"2018-12-10T16:30:03Z","activities":[],"keywords":"JavaScript, React, web3.js, redux","current_bounty":true,"value_in_eth":"1500000000000000000.00","token_value_in_usdt":"692.10","value_in_usdt_now":"1038.16","value_in_usdt":"1038.16","status":"open","now":"2019-02-18T16:03:21.824889Z","avatar_url":"http://localhost:8000/dynamic/avatar/unlock-protocol","value_true":"1.50","issue_description":"The `keyPrice` for each Lock is set upon creation of the `Lock` smart contract.\r\nWe expect most creators to actually \"price\" the keys to their lock based on a fiat value ($ or else). As such we should allow creators to update the price of the keys (`keyPrice`) on the locks easily at any point. This will require additions to the Lock smart contract but also changes in the web app.","network":"mainnet","org_name":"unlock-protocol","pk":1512,"issue_description_text":"The `keyPrice` for each Lock is set upon creation of the `Lock` smart contract.\r\nWe expect most creators to actually \"price\" the keys to their lock based on a fiat value ($ or else). As such we should allow creators to update the price of the keys (`keyPrice`) on the locks easily at any point. This will require additions to the Lock smart contract but also changes in the web app.","standard_bounties_id":1844,"web3_type":"bounties_network","can_submit_after_expiration_date":true,"github_issue_number":138,"github_org_name":"unlock-protocol","github_repo_name":"unlock","idx_status":"open","token_value_time_peg":"2019-02-18T15:49:27.180647Z","fulfillment_accepted_on":null,"fulfillment_submitted_on":null,"fulfillment_started_on":null,"canceled_on":null,"canceled_bounty_reason":"","action_urls":{"fulfill":"/issue/fulfill?pk=1512&network=mainnet","increase":"/issue/increase?pk=1512&network=mainnet","accept":"/issue/accept?pk=1512&network=mainnet","cancel":"/issue/cancel?pk=1512&network=mainnet","payout":"/issue/payout?pk=1512&network=mainnet","contribute":"/issue/contribute?pk=1512&network=mainnet","advanced_payout":"/issue/advanced_payout?pk=1512&network=mainnet","social_contribution":"/issue/social_contribution?pk=1512&network=mainnet","invoice":"/issue/invoice?pk=1512&network=mainnet"},"project_type":"traditional","permission_type":"approval","attached_job_description":"https://unlock-protocol.com/jobs","needs_review":[],"github_issue_state":"closed","is_issue_closed":true,"additional_funding_summary":{},"funding_organisation":"Unlock Inc","paid":[],"admin_override_suspend_auto_approval":true,"reserved_for_user_handle":"","is_featured":false,"featuring_date":null}]