Topic: [DVC]DevCoin - Official Thread - Moderated - page 184. (Read 1058949 times)

No sheeeeeeet :O 500 would be all time high :|

Wolong appears to be pumping it: https://twitter.com/GameOfDeception

Planning to take it to 500 satoshi or maybe even more

Any news that caused todays price increase?

Wow look at the devcoin price!
-AM

    DEVCOIN - ON POSITION 5 - TRADING ACTIVITY ON CRYPTSY.COM

   
    Here Cryptsy Live Statistics - http://live.myip.ms

DVC/BTC going to the MOON 

Did you have to change the makefile to make it compile for ubuntu or was it ootb?

The pro file will prob need revision to make it compile for linux.. I think emfox did it but had issues.

The main difference is in devcoin you have block headers which contain auxpow data instead of being a constant 80 bytes or whatever.

Refer to https://en.bitcoin.it/wiki/Merged_mining_specification

The old devcoin blocks and new ones should be the same as the new client is backwards comptable.

Any header parsing will break in armory.. u need to parse AND validate the auxpow header section following the spec.

The diff algo is different.. devcoin averages previous blocks.. so you need to ensure previous block data is available to even check the diff target. I ran into issues on android wallet since bitcoinj didnt need previous blocks and it starts downloading blocks after it reaches a certain date (release of wallet) so before that it only downloads headers or diesnt need to download any data at all for optimization purposes.

Armory probably does this aswell since it doesnt need blocks before it was created.

Its a simple fix.

The fees were changed to 5 coins too.. and make sure the getminfee function is right. In android its hardcoded to 5coins per 1kb tx size.

To ensure there is no way that the tx doesnt get thru due to insufficient fees. Devcoind bitcoind have this allowfree thing that android wallet doesnt knownsince it doesnt generate blocks.
 
Jag

please post your step of compiling, and the exact error message.

Okay sounds good. As far as I can tell most of the substantial changes were in 0.8.x; there are lots of places in the code that reference that version. I just started working on it, so I got it talking to devcoind, and reading the blocks from blk0001.dat instead of the blocks folder, but I'm realizing that most of the changes I'm making to get it to read devcoin blocks are just reverting changes that were made for post 0.8 bitcoin. I think it will be a lot easier once I get the 0.8.5 based devcoind built.

I guess I'm not fully aware of all of the difference between the devcoin and bitcoin blockchains, I assumed that all I would have to change is parsing of the receiver files - although Armory interfaces directly with bitcoind/devcoind, so maybe that would be handled by devcoind rather than by Armory. If I have any trouble I'll definitely refer to your Android wallet or send you a PM.

Now I'm going to see if I can the new 0.8.5 wallet compiled on Ubuntu.

Edit:

For what it's worth, I have the 0.8.5 devcoind compiled and running on Ubuntu 12.04, got the whole blockchain downloaded successfully and I imported my wallet and the balance looks normal. Anything specific you'd like me to test?

Btw is there anyway to compile Devcoin-Qt on Linux? Or is that not supported yet? I'm getting a lot of errors when trying to use the "bitcoin-qt.pro" with QTCreator.

coinzen does not appear to support https connection so i'll be unable to access it. it looks like user registration doesn't support it either. for a cryptocurrency it is important that forum discussions occur over encrypted medium so that text is not changed by third parties.

Ok, thanks for that, i will try it.

Tenthirtyone made all the devcoin subforums, so devcoin is moving to coinzen! Please make a coinzen account if you haven't already:
http://coinzen.org/index.php

The main devcoin thread is:
http://coinzen.org/index.php/topic,147.0.html

Today I'll make Support threads and Bounty threads. Over the next week we'll make threads for everything else. This thread will be watched a little for the next month, to direct people to the new coinzen threads.

Please make it work with new code which is ported to 0.8.5, but it will have to be forward ported again to 0.9.0 when we merge that code in later. We are just testing the merged-blocks are backwards compatible across clients. The windows client is in test mode, and linux client can be built aswell from source...

https://github.com/sidhujag/devcoin

I did the android wallet based on 0.8.5 aswell... are there changes in Armory after 0.8.5? Otherwise you can use this code as your client to test with. (version is now 70001 from 032501 or whatever)

How are you going about it? just adding the merged-mine parsing, and do similar adaptions that the client did with bitcion -> devcoin?

Hi

Anyone else having trouble posting new stuff or making edits on devtome?

It was fine until about 36 hours ago, but now every time I try an update it hangs - although interestingly navigation to view articles that are already published is fine.

Hey all, what's the status of porting Devcoin to the 0.8 source? From what I can tell there is a Windows build, but nothing for Linux yet?

I've been working on making Armory work with Devcoin and it looks like Armory already removed a bunch of support for older versions of Bitcoin. If I spend time making Armory work again, I may just have to change it back when Devcoin is updated to the newest source. Should I wait til the new wallet is ready or just move forward making Armory work with the current Devcoin?

The issue isn't with a lack of admins. I'm not your writing admin so I can't confirm, but maybe you were flagged for something. If you want to toss me a PM with more information I'll forward it up and see what happened.

LOL weisoq--I totally missed the post. Lucky for me I had no objections

I was reading some of the more recent posts about support or the lack thereof, and here's my take on it:

1. People are generally willing to help, even if it's not exactly something they get paid to do, so team spirit is high. Exceptions seem to be few and far between and probably can be dealt with case by case.

2. Some of us (yes, yours truly included) don't always keep up with the forum so might miss support requests we can answer. Even when we do, it's easy if we're in a hurry to hope someone else answers the question first (and often that does happen). So it's possible this thread may not be the best place to post these requests.

3. For me PM's are a sure way to reach me, because even if I'm not on the Forum for a few days, I get the notification in my email. Then when I want to address them, I log onto the Forum and all my support requests (mostly signup requests) are in one place, not mixed in with my other emails. So if I'm the person to ask, then PM is the best way.

4. Having said that, PM is not the best way to get immediate support from me as I may not get back to the request for a day or two, so I generally encourage users to post their questions to the thread saying someone else might get to it sooner than I will, but I make an effort to still answer their question as soon as I can.

5. Even though we're all a team and there's a lot of cross help, it would be helpful to have something like an About Us page on the Devtome that is prominently linked to from the front page. This page would have a headline section for each admin and what each one does and his or her preferred contact method. For example for me, it's via forum PM, but for others it might be a specific email address, social media ID or text message, etc.)

6. We also have a prominently linked Devtome page that is organized by the various support needs users might have, and each section includes options on how to go about getting that support. In some cases it may be reaching out on this thread, but other cases may involve PM'ing a specific admin, or even sending a PM to a specific group of admins.

7. We also have a prominently linked Devtome page for updates/announcements/changes. Admins can make a point to check it regularly so they know when changes happen (if like me they missed it when it was announced here). When a change is posted on the announcement page, it should also be populated on any other policy pages so that all info is consistent. So for example, any pages which mention a writer share count limit of 80 should be changed to 50.

If there are no objections I'll go ahead and create an about us page and ask admins to post their own info once I have a good format down. At first admins will be listed in no particular order, but as more info is added I'll organize it into some logical fashion, grouping like admins together.

If there are no objections I'll create a page for common support issues and how to resolve them, again with the commitment to organize it in a logical manner once info gets added. I would ask admins who mostly deal with a certain type of issue to fill in the info about the issue and how to resolve it. This page could read like an FAQ page.

If there are no objections I'll create an update/announcement page, and this one will simply be maintained where new announcements get added to the top (like a blog).

I won't invoice any of these pages since most of the content will not be created by me, just organized.

Well, I got contacted and added to the list and everything. I started posting like in the middle of the round. But I want to make sure it's not a layout glitch that is making tomecount ignore those entries.

On a similar note as my last post, since the suggestion for dedicated help position was rejected, how about we add more admins and/or devtome reviewers? The devtome word count doubled last round and is likely to double again this round with the high dvc price.

Thoughts?

You're lucky, none of mine got in this round. There is a week long process and each new writer needs to be checked by 3 different people AFTER you post your first 1000 words.

I singed up for devtome few weeks ago but didn't post anything just wrote my articles in word instead of the wiki thinking that I was ok if I post them by the deadline. Didn't know about the 1000 words rule.

Basically, everything that doesn't get in round 32 will transfer into round 33.

With the influx of new writers the process is going very slow, I have yet to be contacted about my devcoin address by an admin and it's over a week now since I started posting on devtome. Nothing to do but wait for the next round I guess.