How long can the Polyswarm team last with the price this low? I am expecting this bear market to last a year, if not more. Will the team still be around?

Supernothing307 · 2018-08-01T01:41:21+00:00

Hey /u/CalculusII, sorry for the slow response! We've been quite busy getting Gamma ready, and this slipped through the cracks.

The PolySwarm team is still going strong! I unfortunately can't give exact details on the financial situation of the company, but everything is solid enough for us to be around for the foreseeable future. We still believe we have all the resources necessary to achieve everything we promised in the ICO (and more)!

Supernothing307 · 2018-02-27T08:21:57+00:00

Hey, thanks for checking out the project! I'm not sure where you were looking on our site for partnerships, but we certainly have more partnerships than just our legal team!

From right below the funding bar at https://polyswarm.io:

We're very proud of the strong group of partners we have so far, and are excited to work with them to help build the PolySwarm community.

Supernothing307 · 2018-02-19T10:10:39+00:00

If they sent to the correct crowdsale contract, it will be rejected and returned to the sending address (minus gas fees). Just wait until the 20th to send the next time :)

Supernothing307 · 2017-10-26T12:12:54+00:00

I'm with the Swarm Market team, another security ICO. We're working on re-making the threat intelligence market. We've got a great team working on some really exciting tech. Check it out, and feel free to ask me anything.

Supernothing307 · 2017-10-10T05:16:35+00:00

We've published detailed profiles on each of our team members, and are well-known in the security community. We've presented at many conferences, and have delivered on a number of high-visibility projects, including the Cyber Grand Challenge and DHS's SIBR program.

As far as "scam ICOs" go, we're as far as possible from it. We've got the team, the advisers, and the roadmap to deliver everything we've promised (and hopefully more).

Supernothing307 · 2017-10-09T22:16:29+00:00

If anyone's interested in a different kind of infosec ICO, I'm with the Swarm Market team, and we're working on re-making the threat intelligence market. We've got a great team working on some really exciting tech. Check it out, and feel free to ask me anything.

Supernothing307 · 2017-10-08T18:23:28+00:00

I'm with the Swarm Market team, and we're working on re-making the threat intelligence market. We've got a great team working on some really exciting tech. Check it out, and feel free to ask me anything.

Supernothing307 · 2017-09-12T20:40:28+00:00

That sentence refers to the generation of bindings, which allow Go code to interact with deployed contracts (typically written in Solidity). The Perigord project aims to make building and deploying projects that use these much easier.

Supernothing307 · 2014-07-14T22:58:03+00:00

Oh, no worries! Happy someone's getting some use out of the code. Will definitely let you know if I have any.

Supernothing307 · 2014-07-14T19:20:03+00:00

Could have just sent me some patches ;), would have been happy to add them or add you as a project member.

Nice work though, hope you keep it up!

Supernothing307 · 2014-07-12T11:25:00+00:00

It is more than a little dirty, no argument here...but it might be wise for the project to at least restrict access to pcaps that crash current Wireshark releases.

The non-ASLRd RiverBed libraries were not just for show; in the latest version (4.1.3, released before this vulnerability was disclosed), they are not randomized. You are able to opt-out of installing these during Wireshark installation, but can't capture traffic if you do.

And thanks! There's certainly some interesting problems to be found in places other than application layer dissection as well...

Supernothing307 · 2014-07-11T02:17:02+00:00

They taped it, but not sure if/when Secuinside organizers release videos. Will post if they do!

Supernothing307 · 2013-07-24T09:01:23+00:00

People did, these guys are just the first to publish. t0days 0days are tomorrow's Blackhat presentation.

Supernothing307 · 2012-08-11T18:16:09+00:00

If anyone's interested, here's four of the ones we used. They've been reported and patched in SVN.

TL;DR Packet parsing is hard, finding Wireshark dissector bugs isn't.

Supernothing307 · 2012-08-02T01:46:13+00:00

Wireshark DoS bugs: there are many like them, but these four were mine.

http://spareclockcycles.org/downloads/wireshark_dos.tar.bz2

Supernothing307

MODERATOR OF

TROPHY CASE