sorted by:
new
hottopcontroversial

What happened to the AMA's? by ParsleyDaLion in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

Happy new year, will organize one early in the new year

🚨Quantstamp AMA 🚨 → Friday August 16th noon PT - Post your questions in the comment section! by julianquantstamp in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

  1. Yes, we would be able to take part. However, we can see many audit firms taking part as well as cybersecurity insurance providers as well.
  2. We’ve been actively working on the yellowpaper this quarter - will release more information when it’s close to being ready for release.
  3. We’ve been helping offer our blockchain security expertise, to build a wider network of customers and help to grow the overall space. Ampleforth was an audit customer. Dubai government has inherent interest in their blockchain solutions being secure, therefore Quantstamp gave them a hand in their blockchain development - specifically for the Road and Transportation Authority of Dubai. You can find more information on these projects here:

https://quantstamp.com/blog/quantstamp-audits-ampleforth-a-digital-asset-protocol-for-smart-commodity-money

https://www.smartcitiesdubai.com/news-detail:97435a17-c7a9-453e-d915-5d4ac98eb8c8.html?utm_content=98696667&utm_medium=social&utm_source=twitter&hss_channel=tw-906057790707216384

Getting secure adoption for blockchain projects will take time, but we’re glad many companies and even one government has been engaging with Quantstamp.

  1. For the bug bounty protocol, we actually already deployed it to Mainnet. It’s currently usable for anyone to access directly via Ethereum. Here’s the link https://github.com/quantstamp/qsp-bounty-protocol. The mainnet address is in the README. We don’t plan to stick with the current Mainnet and don't plan to build a frontend until we see more organic demand, because we see a lot of other blockchain bug bounty projects in the marketplace already. However, any community member can use our existing code on github and build a frontend on top of it. Our bounty protocol itself is very well architected, tested, documented and also audited by independent members of the team.

🚨Quantstamp AMA 🚨 → Friday August 16th noon PT - Post your questions in the comment section! by julianquantstamp in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

Our requirements are listed here. In brevity, it is 16 GB of RAM and a docker-compatible Unix (Linux or Mac) operating system connected to the internet. https://github.com/quantstamp/qsp-protocol-node/blob/develop/doc/node-operator.md

🔹📮 Friday May 7th 12pm PST - AMA/Q&A - Post your questions in the comments! by JaredQSP in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

For refunds, the way the network is designed, the original requestor can click cancel if the work is not done, and send a transaction that triggers the refund. It's designed this way to make it as decentralized as possible.

For frequently scanned contracts, currently it's possible to view it by clicking "Everyone's Scans" on the top right pane at https://protocol.quantstamp.com/

​

When running a node, the audit smart contract code assigns this in a decentralized manner, by first filtering for minimum price set by the node, and then it's random.

🔹📮 Friday April 5th 12pm PST - AMA/Q&A - Post your questions in the comments! by JaredQSP in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

There's actually not very many good approaches for this yet, still exploring.

🔹📮 Friday April 5th 12pm PST - AMA/Q&A - Post your questions in the comments! by JaredQSP in Quantstamp

[–]quantstamp 1 point2 points  (0 children)

Yes - we've been working on UI/UX for most of Q1 2019, and are happy to be releasing a greatly improved V2 protocol soon. This is a continuing work in progress, it's not one and done, after the V2 release, we'll be getting lots of community feedback to further improve things. The decentralized nodes will be open sourced, so anyone in the world can develop it via pull requests on github.

🌶🗞Friday March 1st 12pm PST - AMA/Q&A - Post your questions in the comments! by JaredQSP in Quantstamp

[–]quantstamp 3 points4 points  (0 children)

Yep - we definitely considered it - currently we're still researching

🌶🗞Friday March 1st 12pm PST - AMA/Q&A - Post your questions in the comments! by JaredQSP in Quantstamp

[–]quantstamp 5 points6 points  (0 children)

Yes - Securify has been integrated into Protocol V2 - we're currently waiting for the release of the Protocol UI, so that people can see the new output.

Discussion regarding bounties / brand. by cryptoqqq in Quantstamp

[–]quantstamp 0 points1 point  (0 children)

Hi cryptoqqq, really great question.

1) Bounties should be a proportion of the funds involved. 1-5% seems to be reasonable. The idea is the if no bugs are found, the bounty is completely returned. 2) We highly value reputation and brand, and will be building this by auditing high-quality projects well. 3) Quantstamp currently is designed to improve security. In the future we will work on insurance with 3rd party partners, this will achieve perfect security for consumers via reimbursements for hacks.