Skip to content
Back to search

smileyCoin

simple web ui to manage mcp (model context protocol) servers in the claude app

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fefergrgrgrg--smileycoin/badge.svg)](/listings/fefergrgrgrg--smileycoin)

HTML

<a href="/listings/fefergrgrgrg--smileycoin"><img src="/api/listings/fefergrgrgrg--smileycoin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 50 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. Smileycoin SMLY
  2. ===============
  3. https://tutor-web.info/smileycoin
  4. Copyright (c) 2014-2016 Auroracoin Developers
  5. Copyright (c) 2017-2020 Smileycoin Developers
  6. What is Smileycoin?
  7. -------------------
  8. Smileycoin is based on the Auroracoin source, so using SHA256, scrypt, skein, groestl and qubit as proof-of-work algorithms.
  9. - 3 minute block targets
  10. - subsidy halves in ~1.22m blocks (~7 years)
  11. - ~50 billion (50 * 10^9) total coins
  12. - 10000 coins per block
  13. For more information, as well as an immediately useable, binary version of
  14. the Smileycoin client sofware, see http://smileyco.in
  15. License
  16. -------
  17. Smileycoin is released under the terms of the MIT license. See `COPYING` for more
  18. information or see http://opensource.org/licenses/MIT.
  19. Development process
  20. -------------------
  21. Developers work in their own trees, then submit pull requests when they think
  22. their feature or bug fix is ready.
  23. If it is a simple/trivial/non-controversial change, then one of the Smileycoin
  24. development team members simply pulls it.
  25. The patch will be accepted if there is broad consensus that it is a good thing.
  26. Developers should expect to rework and resubmit patches if the code doesn't
  27. match the project's coding conventions (see `doc/coding.txt`) or are
  28. controversial.
  29. The `master` branch is regularly built and tested, but is not guaranteed to be
  30. completely stable. [Tags](https://github.com/smileycoin/smileycoin/tags) are created
  31. regularly to indicate new official, stable release versions of Smileycoin.
  32. Community
  33. ---------
  34. https://bitcointalk.org/index.php?topic=845761.0;all

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.