Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Delinquency

Pages: [1] 2 3 4 5 6 7 8 ... 25
MemoryCoin / Re: [ANN] - GPU,CPU(yam) - The Awesomest Pool!
« on: November 30, 2014, 10:14:17 pm »
Pool down?
Pool does not support Memorycoin anymore.

MemoryCoin / Re: Hard-Fork has taken place. V3 is active!
« on: November 07, 2014, 04:31:44 am »
Alright now we just removed temporal retargeting because it was was intermittent on our network.

Here are the provided precompiled executables:




MemoryCoin / Re: Hard-Fork has taken place. V3 is active!
« on: November 05, 2014, 11:34:42 pm »
Memorycoin was great for some months but time goes on.
I would appreciate it to see you working with the BitShares community instead of wasting your time on this...

There will be time for that eventually, Vato.  :P

MemoryCoin / Hard-Fork has taken place. V3 is active!
« on: November 05, 2014, 01:11:21 pm »
For details and download information, please find the Memorycoin Wallet Thread here:

Thanks to everyone who waited for it!
More details about this hard-fork are coming up very soon.

MemoryCoin / Re: [ANN] - GPU,CPU(yam) - The Awesomest Pool!
« on: October 30, 2014, 11:18:37 am »
Current net is running on code from github..

MemoryCoin / Re: [ANN] - GPU,CPU(yam) - The Awesomest Pool!
« on: October 29, 2014, 10:48:46 pm »
MMCPool CPU and GPU miners have not been updated for the v3 hard fork and do not collect work, and the User Earnings page has also stopped updating. Is there a fix in the works?

For the record, I generally CPU mine using the YAM customized miner, which did get an update 4 days ago. I continue to use the MMCPool GPU miner but at the moment can't task that portion of my mining rig.
The pool only needs to update source code to continue accepting GPU shares:

MemoryCoin / Mining Pools and Code Status
« on: October 29, 2014, 01:21:00 pm »
I don't believe that MMCPOOL and 1GH got the memo about our change in source status. The source is staying open, however a few changes we implemented still had some crucial testing to do to make sure the network won't collapse.

The current source, which was updated to reflect pre-v3 conditions while we hammer these bugs out, are located on the github repo:

For now, the most active pool on the network is located at:

If you would like to take advantage of the decrease in network power due to the shutdown of GPU pools, please redirect your miners.

How to connect on YAM:
mine = stratum+tcp://[email protected]:8080/mmc
mine = stratum+tcp://[email protected]:8080/mmc

mine = stratum+tcp://[email protected]:80/mmc

How to connect on minerd:
minerd.exe --url --user YOURADDRESS --threads x
minerd.exe --url --user YOURADDRESS --threads x

minerd.exe --url --user YOURADDRESS -threads x

How to view Pool Stats:

MemoryCoin / Re: Memorycoin wallet no block source available
« on: October 22, 2014, 04:02:27 pm »
Suggestion: CNO should set up a proper DNS seeder.
About v3:

The new code has over 20 churn nodes included with custom code to allow non-default ports to be connected to.

Standard nodes are also included ( around 10 of them ).

If you run a churn or standard node 24/7 please verify your IP and port so we can add it to the final release versions.

MemoryCoin / Re: Memorycoin wallet no block source available
« on: October 22, 2014, 10:10:29 am »
Hi Jure,
please see this link for a tutorial on how to fix the problem.

MemoryCoin / V3 Hard Fork
« on: October 20, 2014, 04:15:34 pm »
Hello Memorycoin Community.

If you had not noticed that the block height is within 300 blocks of  reaching our announced hard-fork checkpoint, without precompiled executables available for download.

On behalf of the Memorycoin Dev. Team, we must push the hard-fork block point by 1680 blocks, or one week.
This will ensure that exchange operators and pools can update their source and compile in a reasonable amount of time.

I'd like to thank everyone for their patience and understanding for the supply issues that we are aiming to fix, and the code is pretty much ready. I don't think exchanges were informed about this hard-fork date, and the network could face problems if the node was not updated by the hard-fork height.

Long Live MMC

You really think your code is that valuable that it needs to be closed? Lol people compete on innovation. Are you saying NoirBits just copied MMC and had no innovation whatsoever?

Interesting that, I seem to remember 3 attempts at communication with my intent being to form a partnership then a merger later. There wasn't much of a response so I went ahead with my plans. I even wanted to use MMC implementation of momentum with an eye for merged mining in the future.

The community as a whole is falling apart due to lack of cooperation between leaders and developers. So to clear the air
1) check the about section of NoirShares you'll see that MemoryCoin devs are mentioned among others.

2 ) let's stop trying to make it on our own, cooperation is a surer bet.

By the way I had asked that you join our meeting and details of the meeting were published on our forum, mentioning NRS and hoping to create a partnership of some kind in the presented material.

It's still available here:

Some of these items have been changed since it was presented so don't worry about the change in supply in that-
Most of those ideas are now in the TODO topic list in the technical section of our closed Officer Board.

Since you've credited Memorycoin for using our code I hope to keep the open source model that we have, and believe that we can trust the open-source community, as long as they credit our code for usage (exactly where it's used).

I shall be updating the code on github shortly with the v3 adjustments.

I've been thinking... so far, I can't see any positive reactions to your announcement. OTOH several people have criticized your decision to go closed source.

Now, you're planning a hardfork. A fork has more than one prong, though. It may well happen that Memorycoin-2 retains the majority of its current users and the Memorycoin-3 fork is largely ignored. What's your plan B for that?

The old network would suffer from faulty supply. The 10 million cap would be hit on the 56th week since launch, not 2 years.

The fixes we have applied are obviously meant to repair the network before that could happen, and suit investors so that the 10 million coin cap is hit after one year, instead of two years.

I have prepared these data based on preliminary work I've done on the code. I created this spreadsheet to outline the future of Memorycoin v2's supply schedule.

The original supply schedule of Memorycoin is described in the spreadsheet below.


Thanks for clearing that up with everyone, emre.

And itsik78 I'm surprised that you still hold your MMC. You think that MMC will go up so you can profit.

Is the fork date/bockno decided upon?

73920, set off at about two weeks from now.

You really think your code is that valuable that it needs to be closed? Lol people compete on innovation. Are you saying NoirBits just copied MMC and had no innovation whatsoever?

No, I just meant that there was no credit given for using our code in their project.

The most valueable BTSX code is opensource   :P

You can secure your credit by a premine or whatever you call it.But close source is a buzz kill.

It'll get you nothing.Without opensource,most exchanges won't even want to enlist.Because they can't be sure what the hell you're doing behind the program.

It's a trade-off that we're willing to accept... There's a huge debate about open-source and close-source but it's actually about the integrity of the current team and the reasons behind the action:

  • Not to secure a pre-mine; but to secure the code from competition that would love it in their "new alt-coin."
  • There isn't much innovation behind our current update but the future updates will have essential code that we would like to protect.
  • We offered current exchanges the source code, as well as for future releases, so there's no issue with exchanges that don't know what we're doing behind the code.

Pages: [1] 2 3 4 5 6 7 8 ... 25