monero-ecosystem / meta Goto Github PK

I would like to introduce monero_health to you. It is written in python and is a module to return health or status information about monerod.

https://github.com/normoes/monero_health

The README describes its usage and responses.

This module is used on the XMR.to community hub - The module provides the running serice with the JSON result.

• https://community.xmr.to/node/mainnet/health/api/v1
• https://community.xmr.to/node/mainnet/health/api/v1/health
• https://community.xmr.to/node/mainnet/health/api/v1/monerod
• https://community.xmr.to/node/mainnet/health/api/v1/monerod/health
• https://community.xmr.to/node/mainnet/health/api/v1/last_block
• https://community.xmr.to/node/mainnet/health/api/v1/last_block/health

The idea is to make the monero daemon status available in a readable format, right now only JSON.

Definition of status (see README):

• There are the P2P and the RPC status - This is essentially about connectivity + information like the hardfork version. Both are combined in the status found at /monerod/health.
• There is the last_block status, which defines an age limit (12 [minutes]) of a block and returns OK if the block is younger than that or ERROR if the block is older than that.

What do you think?

The python module monero_scripts can be found here:

• https://github.com/normoes/monero_scripts
• https://pypi.org/project/monero-scripts/

It is more or less a collection of scripts in order to tackle the 3 (at the moment) following use cases:

• Get the hard fork dates from github/monero-project from within src/hardforks/hardforks.cpp.
• Get the seed nodes from github/monero-project from within src/p2p/net_node.inl.
• Check the P2P connectivity.

monero_scripts is used on the XMR.to community hub to provide hard fork and seed node status information:

• https://community.xmr.to/xmr-countdown/
• https://community.xmr.to/xmr-seed-nodes

Hi, I'm interested in moving monero-wallet-java to this ecosystem.

It provides a Java wrapper to monero-wallet-rpc and monero-daemon-rpc. Support for v0.12.3.0 is almost done then I'll turn attention to v0.13.0 updates.

Probably not worth the trouble if the monero-ecosystem effort is about to be migrated to GitLab, but what would the migration entail? Thanks.

Hi,

As the main author, I'd like to move the repository of monero-python to the Ecosystem. It's version 0.5, a functional beta, which already allows to perform all base operations on a wallet:

• check balances,
• query for incoming and outgoing payments,
• send transfers,
• process mnemonic seeds,
• generate subaddresses offline,
• do address validation and integrate payment IDs,
• do some less important but nice stuff.

However, due to tight schedule and limited net access in the coming weeks (or months), I'd like to make sure all automatic stuff moves also, without too much configuration hassle. In particular I mean Travis CI and Readthedocs. Has someone dealt with those and can outline the transition?

This is a Rust client for the wallet and daemon RPC that I created for the purpose of easy and type-safe integration of Monero into Rust-based web services. While it closely mirrors jsonrpc protocol documented in the Developer guides, it strives to be as Rust-idiomatic as well.

https://github.com/vorot93/monero-rpc-rs

Monero Outreach is working on educational material for the community. The Contribute repository is where all the documentation will be forward for translations.

https://github.com/monero-outreach/Contribute

:)

Thank you.

hello dear monero community,
I have written a client for the monero RPC (wallet and daemon) in golang.

I'd like to add it to the monero ecosystem :)

you can find my repository at https://github.com/omani/go-monero-rpc-client/

https://github.com/graft-project/graft-ng

PoS based Supernode layer for Monero. Real-time authorizations and DAPI.

We have completed the DHT based communication, Authorization quorum selection, Blockchain based list based disqualifications.

Checking on the interest in Monero ecosystem community to take on and maintain what we've developed.

See monero-ecosystem/dont-buy-monero-sticker#17

Reddit user /u/hapticpilot created a script to submit raw Monero transactions over Tor. He asked me to propose to add it to the Monero-Ecosystem project, so i'm opening the request on his behalf. Read the discussion on reddit

It's a simple bash script, and i temporarely uploaded it on my personal repository. If the members of this project feels like it, it can be transferred to the ecosystem. It needs maintainers, so, in case, any volunteer?

submit-tx-via-tor

https://github.com/lalanza808/docker-monero-node

?

Hi guys,
I would like to bring to your attention my freshly created CCS Proposal for a new project of mine:

The Monero Tip Bot for Telegram.

Notice the section where I mention the Monero Ecosystem and my plan to put this project under the umbrella of the Monero Ecosystem, like I did recently with my Go Monero RPC Client.

https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/86

I hope you guys support me in my funding or give me a thumbs up and upvote the proposal.

See you there :)

Cheers!

https://github.com/lalanza808/xmr-node-cannon-do

As initially suggested in #75

ping @lalanza808

http://www.nothisispatrik.com/2018/03/30/python-reimplementation-of-cryptonights-hash-function/

http://nothisispatrik.com/slow-hash.py

Should be added to the list, however can't find this code on github.

I proposed @ehanoc to add Pymonero to the Monero Ecosystem and he agreed. See monero-project/monero#4996 (comment).

Pymonero is a fork of monero-project/monero to deliver python c++ bindings, maybe @ehanoc can tell us more about the project and its goals.

pinging @monero-ecosystem/maintainers as per our governance system. Please express your opinion.

All Kovri repositories have been already moved.
Personally, i'm in favout of moving to GitLab for many reasons, but i would first wait to see what happen to the main Monero repositories. If the project will be moved, i think we should move as well.
opinions? @monero-ecosystem/maintainers

see monero-project/meta#236

In order for Bisq to adopt the monero-java project, Bisq developers have requested its artifacts be uploaded to the Maven Central Repository. Discussion on that here: bisq-network/bisq#3275

I have opened a request to have those artifacts added to the Maven Central Repository: https://issues.sonatype.org/browse/OSSRH-51699

In turn, the hosting provider has requested that we create a public repository named OSSRH-51699 within github.com/monero-ecosystem in order to verify ownership of that project space.

This issue requests a public repository be temporarily created in the monero-ecosystem in order to verify ownership of this project name space.

It appears I am able to create the repository myself, so I will proceed shortly unless there are any objections?

Hi, I am wondering if it makes sense to add my project, monero-cpp-library, to the monero-ecosystem?

monero-cpp-library is a C++ version of monero-java and monero-javascript. It provides a C++ library for using a Monero wallet by wrapping Monero Core's C++ wallet, wallet2.

monero-cpp-library conforms to the same API specification used in monero-java and monero-javascript. It is used by monero-java to provide a full wallet in Java using JNI native binding to Monero Core.

It is my hope that this library may form the basis of adding a new wallet interface to monero-project long term for the wallet RPC server, GUI, and application developers to build on top of.

Thoughts?

I've been working on Monero-History-Box for some time now, and it's in a fairly playable state. The game is a recreation of Candybox, and will hopefully continue expanding with great memes and references to historical components of the Monero community.

It's a little different from most ecosystem projects; it's in a super basic state and really easy for new users to contribute to right now, and has a lot of potential to expand.

Thoughts?

vanity-monero is a CLI tool that generates vanity Monero address.

See https://github.com/Equim-chan/vanity-monero and https://www.reddit.com/r/Monero/comments/8o8wdz/i_just_wrote_a_vanity_address_generator_for_monero/

The "monero-meetup-kit-localization" and "Monero-Flyer" repos will be merged with the "outreach-docs" repo. This issue will be used to track the progresses.

Related issues: monero-ecosystem/monero-meetup-kit-localization#34 and monero-ecosystem/Monero-flyer#2

Hi Maintainers, we really need to decide in which way new repositories should be added to the ecosystem. My proposal:

The team making this decision should be composed by all repo maintainers inside the ecosystem (5 at the moment, 6 soon), but i would keep a veto right as steward of the project (to be used only in extreme cases).

Proposals to add and remove a new repository should be posted here on meta using the issue tracker (and the label repo proposal). A repository will be accepted once at least 50%+1 of the maintainers specifically approve. To approve a new repository maintainers should comment with ACK ("Acknowledged"), to disapprove: NACK (Not Acknowledged).

I added all repo maintainers in the @monero-ecosystem/maintainers team, so that when a feedback is needed we can just ping that team.

Thoughts?

I think the Monero community would benefit greatly from a plug and play Full node that can run on a small low power device 24/7 such as the Raspberry Pi (other boards can easily be adapted to from this project).
It would be a great asset for a user to run their own node they can trust and connect to for making transactions as Privately as possible.

I've built the foundations for this but am at my technical limit, I still want to continue developing it but need the help of others for it to reach it's potential.

It currently is at a stage where it runs the full node and feeds back statistics to a web-ui with details on connected nodes, transactions and sync status, all plug and play to that point.

Development is needed to make it suitable for external connections, user buttons for simple/common features. Configuration for the static IP. And a first boot menu for password setting. All of which I'm sure are simple projects for our community.

More info on the project here:
https://www.pinode.co.uk/monero-plug-and-play.html

Github:
https://github.com/shermand100/pinode-xmr

(And if anyone is familiar with raspiblitz for Bitcoin Lightning this is my target for quality/simplicity for basic users I would like to aim for https://github.com/rootzoll/raspiblitz I don't think it will take too much more to get that standard)

Hi,

I have created python-monerorpc.

It is a fork of python-bitcoinrpc and was adapted to be used wirth monero daemon rpc and the monero wallet rpc.

Example:

rpc_connection = AuthServiceProxy('http://{0}:{1}@127.0.0.1:18081'.format(rpc_user, rpc_password))
info = rpc_connection.get_info()

Maybe you could have a look at it and add it to the monero-ecosystem eventually.

That would be great.
Have a nice day.

Repo proposal

https://github.com/seibelj/iCryptoNode

i have an attachment to this, as that whole thing is what my original monerodo OS was supposed to do. It turns out I just suck at coding. This cryptonode guy doesn't seem to suck.

That's it, we need one. If somebody can make it or have ideas, please comment.

Right now they are in chronological order, but i think would be better to have them separated into different categories, for example 'Documentation', 'RPC clients', etc. The order in which they were included in the Ecosystem is not really important.

hi folks,
do we have a youtube account? I would like to be able to publish my videos related to my projects to a common place on youtube. favorably a monero-ecosystem youtube channel.

do you like this idea? if not, where can I upload videos to my projects and link them in eg. my readmes, links, etc. (in regards to the monero-ecosystem)?

if you do like the idea, let's talk about who will control or own the youtube channel and who will be in charge of maintaining it. and who will be the person to speak to if the @monero-ecosystem/maintainers want to upload a video in general.

and please don't rush and go and enthusiastically create a channel and say "look guys. I just created one. let's use this". anyone can do that. that is not the point.

let's just first talk about it.

thanks
omani

hello folks,

here it finally is:
here is https://github.com/omani/go-telegram-monerotipbot from the successfully fully funded CCS proposal.

the repo is empty. and I will push the code as soon as we moved this (empty) repo to the ecosystem. I do this for operational reasons and Im sure you all understand why.

The final go-telegram-monerotipbot pointing to the monero-ecosystem (URL) will be placed into the README and START notification of the bot (in telegram you see a start message when you start a bot).

The bot is going live (mainnet) tomorrow (sunday) at 9pm UTC. I am glad we finally found a trustfully member of the community who will host the bot and who wants to remain anonymous (for obvious and understandable reasons).

Thank you all for all your support.

cheers!
sun

hello dear monero-ecosystem,

the funding of the monero tip bot is almost done and many milestones were reached.

I took the time to do some refactoring (since I will open source it as stated in the CCS). I want to let it run for a final testing on stagenet for a while to see the outcome of the refactoring.

meanwhile....

I want to use the chance to discuss a very important topic and that topic is:
the trust building of the bot when we go on mainnet. in my CCS I proposed to deliver the bot to the core team if the core team would be willing to do it. unfortunately after speaking to a few of them including fluffy, and not being able to resolve that part of the deal, I decided to reach out to the monero ecosystem since I'm not only a happy member of this team but I also see the opportunity for us to push something forward here. my main thought was, that we are equally trusted as the core team (hopefully) and it's just that we have a different name.

now here are my concerns:
as soon as we open source the code of the bot, practically anyone will be able to host his/her own Monero Tip Bot on telegram. and as we all know - especially in the crypto space - nothing is safe and secure and all well. means, expect that people will abuse the bot by scamming other peoples money (monero). since the bot offers a service of a custodial wallet (the hoster has the private keys), we need trust in the community.

so we have to build a trusted environment for the people who got pretty used to the currently running monero tip bot on stagenet, which grows with a rate of ~5 users per day. (to give you guys some numbers).

this is why:

• I want to announce that the "official" monero tip bot will be hosted and maintained and run by the monero-ecosystem. what is important here is that it is not important (at all), who (which person) will host the bot, in terms of PR (public relations) or the announcement.

the important thing for the people out there is just to know that there can be many copies of this bot, but the one and only you can really trust is the "official" monero tip bot run by this very monero ecosystem team that delivers high quality products <- this is my long term goal btw.

so with this issue:

• I want to clarify my incentives
• what Im thinking an announcement should look like
• the importance of a trusted member or team that people can trust and rely on
• by - in the same time - radiating out to the public that further improvements on the monero ecosystem is important
• deliver the message that we - as a team - each one of us is important and we as a team do coexist with the core team and package the good and important stuff around monero and the ecosystem of it. we can be as equally trusted as the core team.
• etc.

I think you get my point. the monero tip bot is the first step in reaching this important step of building trust. and for many more to come in the future.

let's discuss this issue. Im looking forward to hearing your opinions and comments.

your omani

Just a heads up, a GitHub page containing jsdoc will be deployed to the monero-javascript project over the next few days. Please let me know if the deployment could interfere with anything.

Perhaps we'd want to reference that documentation somewhere, along with the documentation for the associated Java and C++ projects?

https://github.com/skftn/qml-xmr

Related to GUI wallet development.

Hey,

Can we add this project to the Monero Ecosystem? Rbrunner7 has reviewed it. Thanks

https://github.com/Agorist-Action/csharp-monero-rpc-client

hi folks,
here it is finally. the Telegram Monero Tip Bot from the CCS proposal https://ccs.getmonero.org/proposals/monero-tip-bot.html

https://github.com/omani/telegram-monerotipbot

happy tipping! :)

@Jasonhcwong asked on reddit to add his reository to the ecosystem: MoneroBox

From the readme:
MoneroBox aims to make a plug-and-play, zero-configuration Monero full node running on a Single-Board-Computer such as Rock64 and Raspberry Pi 3

Waiting for the author to write on this thread some more info about the project.
Opinions? Questions?

@monero-ecosystem/maintainers

edit: added correct link to reddit comment

This is a tipping service I've been working on for months now, always polishing the UX and constantly adding more features. It is built using monero-python, is non-custodial so users have access to their private keys, and has over 40 Reddit users (and counting).

You can see the version history in the readme of the repo below, and v0.8 will also be coming out soon :)

https://github.com/dginovker/MoneroTipper

Related issue: monero-ecosystem/dont-buy-monero-sticker#17

I'm rewriting the readme, i will add this change in the PR. Opening this issue to announce it to the Monero Ecosystem community and to track the progresses.

I have written a script to extract past and future (if available) hard fork dates.

It extracts the dates from /src/cryptonote_core/blockchain.cpp in the monero repository:

• The repository branch can be configured (master, release-v0.14).
• The network_mode can be configured (mainnet, stagenet, testnet).
• The daemon can be configured (node.xmr.to).
  • This is used to get the block's timestamp (using th method get_block_header_by_height).

It's just a script, so I am not sure, whether it makes sense to add it here.
Altogether it's quite useful.

Here you can find the script:

https://github.com/normoes/monero_scripts/blob/master/get_monero_hard_fork_info.py

You can see it in action here (the output is used):

• https://community.xmr.to/xmr-countdown/
• https://community.xmr.to/xmr-countdown/testnet/
• https://community.xmr.to/xmr-countdown/stagenet/

The countdown starts at 0, because there is no "future" (Version 12) hard fork defined, yet.

This is the output for mainnet:

Version 1 ['Apr 18 2014 UTC', '1', '1341378000']
Version 2 ['Mar 23 2016 UTC', '1009827', '1442763710']
Version 3 ['Sep 22 2016 UTC', '1141317', '1458558528']
Version 4 ['Jan 10 2017 UTC', '1220516', '1483574400']
Version 5 ['Apr 14 2017 UTC', '1288616', '1489520158']
Version 6 ['Sep 16 2017 UTC', '1400000', '1503046577']
Version 7 ['Apr 06 2018 UTC', '1546000', '1521303150']
Version 8 ['Oct 18 2018 UTC', '1685555', '1535889547']
Version 9 ['Oct 19 2018 UTC', '1686275', '1535889548']
Version 10 ['Mar 09 2019 UTC', '1788000', '1549792439']
Version 11 ['Mar 12 2019 UTC', '1788720', '1550225678']

At the moment the announcements on Twitter are mostly made by my personal account, but i think would be better to make them with an account of the Ecosystem. What do the @monero-ecosystem/maintainers think about it?

I think the account should be managed by at least two members of the Ecosystem. DO you think is a good idea? Whowould be up for taking care of that? I could be one of the (at least) two, but i would prefer somebody else to be the active 'maintainer.'

https://gitlab.com/whonix/monero-gui

monero-javascript, monero-python and monero-java all follow the same name to imply they're libraries for the Monero RPC(s) in their respective language, but monero-rpc-rs and go-monero-rpc-client don't follow suite. Thoughts on changing this?

hi folks,
another repository of mine. A xmr.to client written in go.

https://github.com/omani/go-xmrto-client

feel free to ask questions or give feedback.

cheers!
sun

I have worked on this repo for months. And I think it's stable enough for adding into ecosystem.
https://github.com/Lafudoci/moneriote-python

This scripts to maintain Monero opennodes DNS records. I have run one for months, and it's already listed on MoneroWorld 18089 opennode (opennode.xmr-tw.org:18089).

So basically I'll continually maintain this script for sure and there are something I'm planing to improve on it:

• Ability to add more reference nodes for stable height determination.
• Subdomains (us, eu, asia) point records by IP's location for better user experience.

Monero-Javascript was recently announced on reddit by @woodser. He already maintain one repository on the Ecosystem and i proposed him to add also Monero-Javascript. He agreed.

From the Readme:

This project provides a modern JavaScript API for a Monero wallet and daemon.

The API currently relies on running instances of Monero Wallet RPC and Monero Daemon RPC. Primary goals of this project are to support a local wallet with client-side crypto and a MyMonero wallet which shares the view key with a 3rd party to scan the blockchain.

Main Features

• General-purpose library with focus on ease-of-use
• Clear object-oriented models to formalize Monero types and their relationships to each other
• Powerful API to query transactions, transfers, and vouts by their attributes
• Extensive test suite (110+ passing tests)
• Fetch and process binary data from the daemon in JavaScript using client-side crypto

I think this is a very cool and high quality project and would be great to have it in the Ecosystem.
Thoughts? @monero-ecosystem/maintainers

Hi,

I have written a python wrapper for XMR.to:
https://github.com/normoes/xmrto_wrapper

You can create orders, track orders and get the recent prices.

It can be used as module and as script and can be installed using pip - Not yet on PyPi, though.

I find that very useful, especially from a developer's point of view. I wouldn't have created it otherwise :)

I created the monero-docs repository in the ecosystem time ago, but it was never used. If it's ok for the maintainers, I think it should be remove it. This for the policy "No dead repos in the ecosystem". (A thumbs up or down is more than enough here, don't think much discussion is needed)

@monero-ecosystem/maintainers

Hi,

I've just released software for monero, see:
https://github.com/selene-kovri/primo-apache
https://github.com/selene-kovri/primo-firefox
https://github.com/selene-kovri/primo-control-center

Is this the kind of thing you're after ? I2P IRC is dead so I can't even tell the good Monero people about it, so moving it to this monero-ecosystem place seems like the next best thing :)

What do you guys think about creating a simple github page for the Monero Ecosystem project?
Every maintainer could have their own section when they can write info about their repository (even just showing the readme would be ok). I would use it a lot for the guide of the GUI, since i could have it online in an html page.
For more info about github page: https://pages.github.com/

@monero-ecosystem/maintainers

To my shame I have to admit that I haven't tried it myself yet; Anyway:

https://github.com/nasaWelder/lunlumo

Now that Coinomi has provided support for Monero BIP39 derivations, feel free to add the (MIT-licensed, fully open source) repo, in specific the monero branch.
This is a useful tool but it also demonstrates compiling some basic Monero code to webassembly which can be used as a basis for real wallet implementations, not the usual RPC-based stuff.

Repo: https://github.com/Coinomi/bip39
Ready for offline use: https://coinomi.github.io/bip39-monero/