A | B | D | E | F | G | H | I | J | K | L | M | N | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | Applicant name | Applicant Slack user name | Bug category | Bug description (The more explicit it will be the better your chances of the companies reference) | Bug screenshot link (Use Imgur or others) | Suggested solution | Approval Status | |||||
2 | 7/6/2017 17:09:12 | stripple | stripple | CoinDash platform bug | Gatehub Ethereum address recognized, but balance incorrectly calculated. Balance shows $0,14 even though the address should hold around 0,1 Eth. | http://imgur.com/a/kJcwN | If exchange addresses are not supported, I think it should be clearly stated for user friendlyness purposes otherwise people will not trust the numbers and outcomes the platform provides. | No | |||||
3 | 7/6/2017 17:16:53 | stripple | stripple | CoinDash platform bug | Coindash website/app is not responsive (doesn't resize) on mobile. Tested on Nexus 4 (768 x 1280 pixels) see attached screenshot. The set sidebar width interferes with the workings of the rest of the site, showing addresses incorrectly and showing cramped graphs. | http://imgur.com/a/1SUIv | Suggestion would be either to make the left menu a slide in menu (with the three stacked bars as is what sites currently use on mobile) or simply but the buttons on top with small screens, placing all graphs, tables, information under each other to conveniently browse from top to bottom on mobile. For sure people will use the site on mobile when Coindash takes off, plus it makes it a lot easier to stay involved with the platform on the go. | Yes | |||||
4 | 7/6/2017 17:46:38 | stripple | stripple | Security breach - platform & DB | By default, excessive information about the server and frameworks used by an ASP.NET application are returned in the response headers. These headers can be used to help identify security flaws which may exist as a result of the choice of technology exposed in these headers. The address you entered is unnecessarily exposing the following response headers which divulge its choice of web platform server: nginx. | http://imgur.com/a/n87Xf | Configuring the application to not return unnecessary headers keeps this information silent and makes it significantly more difficult to identify the underlying frameworks. | Yes | |||||
5 | 7/6/2017 17:53:30 | stripple | stripple | Security breach - platform & DB | Websites are at risk of a clickjacking attack when they allow content to be embedded within a frame. An attacker may use this risk to invisibly load the target website into their own site and trick users into clicking on links which they never intended to. An "X-Frame-Options" header should be sent by the server to either deny framing of content, only allow it from the same origin or allow it from a trusted URIs. It doesn't look like an X-Frame-Options header was returned from the server which means that this website could be at risk of a clickjacking attack. | http://imgur.com/a/80Qon | Add a header to explicitly describe the acceptable framing practices (if any) for this site. | No | |||||
6 | 7/6/2017 18:07:51 | stripple | stripple | Security breach - platform & DB | HTTP Strict Transport Security not enabled. HTTP Strict Transport Security (often abbreviated as HSTS) is a security feature that lets a web site tell browsers that it should only be communicated with using HTTPS, instead of using HTTP. If disabled, people browsing this server may have credentials intercepted by third parties. | http://imgur.com/a/eMH08 | Enable hsts, for instance using; https://raymii.org/s/tutorials/HTTP_Strict_Transport_Security_for_Apache_NGINX_and_Lighttpd.html | No | |||||
7 | 7/6/2017 18:44:30 | stripple | stripple | CoinDash platform bug | No Public Key Pinning. Public Key Pinning means that a certificate chain must include a whitelisted public key. It ensures only whitelisted Certificate Authorities (CA) can sign certificates for *.example.com, and not any CA in your browser store. In short, it prevents man-in-the-middle-attacks. | http://imgur.com/a/p1zk1 | Configure using this guide for instance; https://raymii.org/s/articles/HTTP_Public_Key_Pinning_Extension_HPKP.html | Yes | |||||
8 | 7/10/2017 12:28:17 | David | danceswithcrypto | CoinDash platform bug | Word misspelled | http://imgur.com/HtzFaei | "characters" not "charachters" | Yes | |||||
9 | 7/10/2017 12:31:50 | David | danceswithcrypto | CoinDash platform bug | No way to view/edit custom token properties | http://imgur.com/T0xCNTh | When a custom token is added, user should be able to edit or view the details (watch contract, number of decimals), in case they made a mistake. Additionally, the 'watch contract' field should enforce unique values within a single portfolio. Duplicates of a custom token should not be allowed. | Yes | |||||
10 | 7/10/2017 12:33:39 | David | danceswithcrypto | CoinDash platform bug | when viewing portfolio balance, token values and quantities are too close together. | http://imgur.com/uvwi0kN | Float the values to the right, to make for a clearer read. | Yes | |||||
11 | 7/10/2017 12:34:43 | Christian Rehnelt | chris_r99 | CoinDash platform bug | if portfolio is removed and another portfolio is added then dashboard is not updated (still the old one). Need to logout and login again | See description | Bug just needs to be fixed | No | |||||
12 | 7/10/2017 12:35:58 | David | danceswithcrypto | CoinDash platform bug | In the token price and the decimals field, failure to enter an integer first results in a "NaN" error. This cannot be edited or removed, you have to cancel the custom token addition and then start over. | http://imgur.com/o08l5vg | This should be editable. Starting an integer with a "." for example ".08" should automatically convert the entered value into a "0.08". Likewise, if an error arises, user should be able to backspace/delete field value to re-enter the correct number without having to close the dialogue box and start the process over. | Yes | |||||
13 | 7/10/2017 12:38:10 | David | danceswithcrypto | CoinDash platform bug | SAN token: When I added the SAN custom token to my portfolio, it immediately calculated a price 2x higher than the current price, creating an inaccurate portfolio graph. Additionally, it values the token (which currently is not trading) at a price different than the price I entered when adding the token in the first place. | http://imgur.com/uNp0mwR | Verify that custom, non-trading tokens show in the portfolio at the entered price, until another price is available. | No | |||||
14 | 7/10/2017 12:39:47 | David | danceswithcrypto | CoinDash platform bug | The button value shows "start calculating..." which implies that it is already calculating and could be confusing for some users. | http://imgur.com/lCZl4uo | Change the text to: "START CALCULATING" or simply "CALCULATE" | Yes | |||||
15 | 7/10/2017 12:39:51 | Jeroen van Beek | jbeek | CoinDash platform bug | Entered Ethereum address to set up and activate portfolio. This worked okay. The I wanted to add another Ethereum address to this same wallet but when I did it would show me the wallet value in that portfolio. Also when I deleted the initial Ethereum address and left in the new it continued showing the old value. The portfolio doesn't seem to refresh based on the Ethereum addresses linked to it. In the image below you can new updated address with the old value | http://imgur.com/KbCEcsk | Automatically refreshes based on the source addresses added in the portfolio | No | |||||
16 | 7/10/2017 12:41:06 | David | danceswithcrypto | CoinDash platform bug | When viewing the portfolio breakdown, the column title "value" is not aligned with the list of values. | http://imgur.com/UbrXJLG | Align the column to be directly over the list of values. | No | |||||
17 | 7/10/2017 12:42:11 | David | danceswithcrypto | CoinDash platform bug | "Identified tokens" title has no margin on the left; making it unaligned with the rest of the page. | http://imgur.com/biwCfsG | Add a margin left equal to the other titles on that side of the page. | No | |||||
18 | 7/10/2017 12:43:47 | David | danceswithcrypto | CoinDash platform bug | Navigation bar tooltips do not show; they flash for a split second when hovering over the link and then disappear. | http://imgur.com/ZNw5jrn | Make it so that tooltips show and stay showing for as long as the mouse hovers over the link. | Yes | |||||
19 | 7/10/2017 12:45:10 | David | danceswithcrypto | CoinDash platform bug | Pressing the recalculate portfolio button in the navigation bar shows no loading indicator, confusing the user as to whether or not the button was successfully pressed. | http://imgur.com/ZNw5jrn | Add a loading indicator to the page in order to clearly show the user that the request has been sent and the portfolio is recalculating. | Yes | |||||
20 | 7/10/2017 15:18:49 | bitbytes | bitbytes | CoinDash platform bug | bitbytes [2 days ago] After removing portfolios, the chart and tokens table do not reflect the removals | upon request | Refresh database after removal with only remaining addresses | Yes | |||||
21 | 7/10/2017 15:20:00 | Bitbytes | bitbytes | CoinDash platform bug | No way to change portfolio name or description after its created | upon request | Edit ability to correct typos or change portfolio name | No | |||||
22 | 7/10/2017 15:23:34 | bitbytes | bitbytes | CoinDash platform bug | When portfolio calculated status “Building performance report”, performnce misspelled | upon request | correct spelling | Yes | |||||
23 | 7/10/2017 15:24:25 | bitbytes | bitbytes | CoinDash platform bug | On initial app.coindash.io page, it’s not obvious that you need to click the coindash logo to enter | upon request | add the words “click to enter” | Yes | |||||
24 | 7/10/2017 15:25:41 | bitbytes | bitbytes | CoinDash platform bug | During portfolio calculation it says “Preparing data for human ingestion” sounds wierd | n/a | Maybe that should be changed to “human readability” | Yes | |||||
25 | 7/10/2017 15:26:43 | bitbytes | bitbytes | CoinDash platform bug | Calculate button gives no idea if a portfolio was already calculated | n/a | Once a portfolio has been calculated, the button should say “last calculated xx/xx/xx at xx:xx am so users know whether to recalc | Yes | |||||
26 | 7/10/2017 15:27:39 | bitbytes | bitbytes | CoinDash platform bug | Chart has only one timeframe | n/a | Time frame is relevant for any investment so user should be able to change to different time frames: Day, 3 Day, Week Month etc | No | |||||
27 | 7/10/2017 15:28:48 | bitbytes | bitbytes | CoinDash platform bug | Using yellow on the chart for ETH benchmark is hidden on the graph when portfolio performs better than ETH | n/a | Don't use opacity or choose a different color, maybe add a line to make the ETH value obvious | Yes | |||||
28 | 7/10/2017 15:43:47 | bitbytes | bitbytes | CoinDash platform bug | Dashboard token list animation does not behave as expected | n/s | It is unclear what clicking does when it triggers the animation - I expected it to change the chart to highlight the performance of just that token vs ETH | No | |||||
29 | 7/10/2017 15:44:45 | bitbytes | bitbytes | CoinDash platform bug | Unclear what contribution each token in a portfolio makes to the total | n/a | It would be nice in the chart if the tokens (which already each have a color) could also each have a line in the chart to stack to a total portfolio line | No | |||||
30 | 7/10/2017 15:45:57 | bitbytes | bitbytes | CoinDash platform bug | When you go through the tour, when you get to 3 if you are on the “allocation” tab it is confusing because it is talking about performance. | n/a | Make the underlying page change to the performance tab when on tour step 3 | No | |||||
31 | 7/10/2017 15:46:48 | bitbytes | bitbytes | CoinDash platform bug | Token prices are different than etherscan | n/a | You should clearly link to the source of price data, so users know where it comes from | No | |||||
32 | 7/10/2017 15:47:48 | bitbytes | bitbytes | CoinDash platform bug | When adding custom tokens in step 2 Symbol there is a typo for the Guidance: Symbol for the token - usally 3-4 charachters in uppercase form; e.g. PLU - “usually” and “characters” | n/a | Correct spelling to “usually” and “characters” | Yes | |||||
33 | 7/10/2017 15:48:43 | bitbytes | bitbytes | CoinDash platform bug | Typing non numbers in Decimals input field in Token Options locks “NaN” into the field which cannot be removed. You just have to “cancel” the whole thing to get out, losing previous inputs | n/a | either don't lock the entry or put an x to delete entry | Yes | |||||
34 | 7/10/2017 15:49:54 | bitbytes | bitbytes | CoinDash platform bug | When removing an address from a portfolio, there is no check that this is the desired action | n/a | Pop up a confirmation “are you sure you want to delete this address” in case it’s clicked by mistake | Yes | |||||
35 | 7/10/2017 15:50:41 | bitbytes | bitbytes | CoinDash platform bug | In step 3 of the tour the window appears below my browser screen and I can’t get to the button to advance the tour | n/a | ensure the modular always appears above the bottom of the screen | Yes | |||||
36 | 7/10/2017 15:51:39 | bitbytes | bitbytes | CoinDash platform bug | On the last screen of the tour instead of the struck out “next” link, it should just say “close” | n/a | Change button to say close and the action would be to exit the tour | No | |||||
37 | 7/10/2017 20:11:13 | Jeroen van Beek | jbeek | CoinDash platform bug | Created new portfolio with Ethereum address but when I click calculate the circle of death appears and keeps rolling. I did this using a Safari browser. Also after logging back in the issue is not resolved | Not needed | Check browser compatibility and ensure that new portfolio, calculate works effectively | Yes | |||||
38 | 7/11/2017 8:07:10 | RecifeCrypto | @recifecrypto | CoinDash platform bug | Hello friends, my account is bugada do not update the twiter statos and neither does my link ICO I thank for understanding ... | https://drive.google.com/file/d/0B2FTvqsMyZxic1FzTlRaZGVEWFU/view?usp=drivesdk | Resolve to the reputational integrity of the coindash | No | |||||
39 | 7/12/2017 2:51:20 | https://bitcointalk.org/index.php?action=profile;u=993592 | no | CoinDash platform bug | Multiple Portfolios for scammers https://bitcointalk.org/index.php?topic=1866838.msg20077765#msg20077765 | no | no | No | |||||
40 | 7/12/2017 6:06:38 | Bob Dylan | bobbydylan | Token Sale contract bug | Missing maximum gas requirement in contract. As well as inconsistency between (60GWEI maximum gas in tutorial) vs. what was told to others on slack (50GWEI). | http://imgur.com/a/VxhaF | Make sure that maximum gas is clearly communicated and in the contract. | No | |||||
41 | 7/13/2017 13:11:11 | Daithi Coombes | daithi | CoinDash platform bug | After adding ecr20 tokens (ticker: MCO) - balance in portfolio isn't updated. Refresh page doesn't help | http://imgur.com/SEV2i9r | This may be a false positive. Maybe feature to track tokens in portfolio totals isn't implemented yet. If not then bug fix should mean that overall portfolio totals include tokens that wallets may own. User goes to dashboard. User looks at portfolio and can see overall value across time in the relevant chart and figures. | Yes | |||||
42 | 7/17/2017 14:11:25 | Hidden | hidden | CoinDash platform bug | When trying to connect Facebook page to Coindash bounty account, an error occures. | http://imgur.com/W0yMIHI | - | No | |||||
43 | |||||||||||||
44 | |||||||||||||
45 | |||||||||||||
46 | |||||||||||||
47 | |||||||||||||
48 | |||||||||||||
49 | |||||||||||||
50 | |||||||||||||
51 | |||||||||||||
52 | |||||||||||||
53 | |||||||||||||
54 | |||||||||||||
55 | |||||||||||||
56 | |||||||||||||
57 | |||||||||||||
58 | |||||||||||||
59 | |||||||||||||
60 | |||||||||||||
61 | |||||||||||||
62 | |||||||||||||
63 | |||||||||||||
64 | |||||||||||||
65 | |||||||||||||
66 | |||||||||||||
67 | |||||||||||||
68 | |||||||||||||
69 | |||||||||||||
70 | |||||||||||||
71 | |||||||||||||
72 | |||||||||||||
73 | |||||||||||||
74 | |||||||||||||
75 | |||||||||||||
76 | |||||||||||||
77 | |||||||||||||
78 | |||||||||||||
79 | |||||||||||||
80 | |||||||||||||
81 | |||||||||||||
82 | |||||||||||||
83 | |||||||||||||
84 | |||||||||||||
85 | |||||||||||||
86 | |||||||||||||
87 | |||||||||||||
88 | |||||||||||||
89 | |||||||||||||
90 | |||||||||||||
91 | |||||||||||||
92 | |||||||||||||
93 | |||||||||||||
94 | |||||||||||||
95 | |||||||||||||
96 | |||||||||||||
97 | |||||||||||||
98 | |||||||||||||
99 | |||||||||||||
100 |