-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forum or mailinglist? #688
Comments
Afaik, no. This repository is no longer being maintained. |
Thanks for the information about the repository. Is there somewhere I can download all of the Wiki documents as well so that I can start a fork of Graphene? Thanks again |
|
Please be aware that, there are many fixes and improvements have been done in the projects forked from this repository, so IMHO it's best to follow those projects directly. |
Thanks for getting back to me.
I actually have been looking at Graphene based project like Steem,
Bitshares, and EOS which seem to be using the Graphene core code and which
I think originally was called Bitshares-1 but have now advanced their code
bases over to Bitshares-2 with some improvements.
I also see that those projects, while good, have added many layers to the
Graphene core code and, for example, have added the ideas of multiple coins
(tokens) within the basic code (Steem has STEEM and Steem Power). I
actually also really like Steem but am still trying to figure out if it is
the est solution for my needs.
For my particular project, I am also looking for a crypto engine that is
capable of extremely high transactions per second and read that Graphene
has the capability to process 100,000 TPS (Network dependent of course).
With that in mind, I was hoping to use a latest and viable version of
Graphene which should be simpler to initially work with than to have all of
the layered changes, but I cannot find any current Graphene fork that uses
just 1 coin at the moment.
On a side question, what is the reason that the Graphene core is not being
maintained and advanced any longer? I think that it's a GREAT product with
great potential.
Cheers and have a great day, my friend,
Lonnie
…On Mon, Jul 9, 2018 at 8:02 AM, Abit ***@***.***> wrote:
Please be aware that, there are many fixes and improvements have been done
in the projects forked from this repository, so IMHO it's best to follow
those projects directly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#688 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXkxHl87GojxWnXlIOOLEz47LlgTgomkks5uE0ZWgaJpZM4VG5ij>
.
--
Thanks and have a great day,
Lonnie T. Cumberland, PhD.
DIRECT: 313-333-2935
Email: [email protected]
|
The code in this repository originally supports creating multiple tokens/coins. If you want to disable that feature, you can
This repository was mainly created for BitShares. But this repository is owned by a private company, namely "CryptoNomex". The BitShares community decided to maintain and advance the code base under an organization account, https://github.com/bitshares. You can search for stories about Daniel Larimer, BitShares, Steem and EOS. |
Thanks again and I will continue to do more research. I have beet been
discussing Steem & Bitshares with some folks and it is truly a complex
setup given the multiple coins/tokens STEEM & Steem Power that make things
very confusing for the users which I was trying to minimize by somehow
using a single coin approach.
One suggestion was that since the Steem Power (VESTS) can be hidden and
used internally so that user is only aware of STEEM coins, and they suggest
that Bitshares is doing something similar already. Maybe that is a pathway
forward for me.
I will now dig into Bitshares more to see what may be done.
Thanks again,
…On Mon, Jul 9, 2018 at 10:53 AM, Abit ***@***.***> wrote:
any current Graphene fork that uses just 1 coin
The code in this repository originally supports creating multiple
tokens/coins. If you want to disable that feature, you can
- remove related code
<https://github.com/cryptonomex/graphene/blob/f1b19b15629cd02669a94f2af16eeaec7f54b3f6/libraries/chain/include/graphene/chain/protocol/asset_ops.hpp#L119-L152>,
or
- set a high operation fee
<https://github.com/cryptonomex/graphene/blob/f1b19b15629cd02669a94f2af16eeaec7f54b3f6/libraries/chain/include/graphene/chain/protocol/asset_ops.hpp#L121-L126>
for it so it will be effectively disabled.
On a side question, what is the reason that the Graphene core is not being
maintained and advanced any longer?
This repository was mainly created for BitShares. But this repository is
owned by a private company, namely "CryptoNomex". The BitShares community
decided to maintain and advance the code base under an organization
account, https://github.com/bitshares.
You can search for stories about Daniel Larimer, BitShares, Steem and EOS.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#688 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXkxHljf-TASMrz_axlTVV7vJQyJbfOcks5uE25lgaJpZM4VG5ij>
.
--
Thanks and have a great day,
Lonnie T. Cumberland, PhD.
DIRECT: 313-333-2935
Email: [email protected]
|
fixed issue cryptonomex#688, add get_asset_count API
Hello,
Is there a forum or mailing list for Graphene?
I know there are various forums for Bitshares, Steem, and EOS, but I am looking for something specifically for Graphene as I want to develop from the Graphene code-base.
Thanks
The text was updated successfully, but these errors were encountered: