Author

Topic: [ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 289. (Read 1201380 times)

legendary
Activity: 882
Merit: 1000
DecHelp is a DecPayments project which aims to raise funds to donate for organizations around the world, this is possible without bureaucracy, using cryptocurrency. Each month is selected an organization, and all donations will be passed to it. Our goal is move the cryptocurrency users to a noble cause, helping to make the world a better place.

You can contribute to this campaign, transfer any value, in Decred, to the project or disclose it: decpayments.com/dechelp.

Organization of the Month: Médecins Sans Frontières (Doctors Without Borders).

newbie account, no proof of that actually happening nor a legit looking website, smells like a scam to me......
legendary
Activity: 1526
Merit: 1000
the grandpa of cryptos
Doctors Without Borders ? Pfff
I'll never donate anything to the masonic organizations.

donating mean they will sell DCR and get USD.

so we will loose in value.
hero member
Activity: 700
Merit: 500
Doctors Without Borders ? Pfff
I'll never donate anything to the masonic organizations.
newbie
Activity: 9
Merit: 0
DecHelp is a DecPayments project which aims to raise funds to donate for organizations around the world, this is possible without bureaucracy, using cryptocurrency. Each month is selected an organization, and all donations will be passed to it. Our goal is move the cryptocurrency users to a noble cause, helping to make the world a better place.

You can contribute to this campaign, transfer any value, in Decred, to the project or disclose it: decpayments.com/dechelp.

Organization of the Month: Médecins Sans Frontières (Doctors Without Borders).
legendary
Activity: 2184
Merit: 1028
#mitandopelomundo
Hello everyone,

The developers have put forward a development roadmap for the software that details short-term, medium-term, and long-term goals. These are actionable goals, many of which already receive active development, but they are considered actionable as development activity in these directions will produce the stated outcomes, which users will see, be able to use, and benefit from in the software.

In the drafting of this development roadmap, it was important not to forecast too far into the future, so that Decred may remain versatile and adaptable to changing conditions in the field. Users can have confidence that these goals are on the developers' minds as they continue working toward them and will begin taking form as progress manifests in the different areas. Attainment of these goals will lay a very strong foundation both through the software and the project upon which to continue building and eventually expand into new areas.

All of these goals aim to work together to establish Decred as a global decentralized network and platform for accessible representation through collective voting and consensus-based decision-making on issues. And that's where it starts.

Short-term (Current) Goals
Daemon
  • Sync in the new database from btcd to prepare for voting on hard and soft forks.
  • Integrate existing Decred consensus rules into the new format inherited from btcd.
  • Demonstrate voting on a simple hardfork.
  • Clean up codebase, extend test coverage, better integrate new btcd features that were quickly merged in.
  • Clean up cryptographic libraries and remove the interface from chainec. Instead, use simple wrappers to reduce overhead.
  • Integrate latest Bitcoin softforks.

Wallet
  • Speed up calls that are heavily used by dcrstakepool, such as getstakeinfo.
  • Add new RPC functionality to the gRPC interface, preparing it for general use.

Governance
  • Make voting simple and easy to use across platforms, from the stake pool to the wallet.
  • Create a website to track voting and easily display information about voting to the end user.
  • Create the initial Decred Assembly and begin making decisions to steer development in public.

GUI
  • Finish the GUI for Windows and polish the externals for presentation.
  • Wire in stake related components of the GUI.
  • Create a one click file to setup and start the GUI, with Tor integration for connectivity.
  • Add a simple functionality to look up and update the daemon and wallet if a new version comes out.

Stakepool
  • Speed up stakepool by using asynchronous calls to the various wallets.
  • Handle situations in which the wallets are desynced without causing failure.
  • Allow external modification of the server's state, e.g. allow triggering maintenance mode.

Scripting language and IDE
  • Finalize the specifications and syntax for the scripting language.
  • Complete the initial implementation of the scripting language, with emphasis on optimization and ease of use.
  • Ensure the scripting language is backwards compatible with Bitcoin scripting, so that the entire Bitcoin-derived ecosystem benefits.

Mining
  • Get gominer functional and into production across multiple platforms.
  • Create specifications and a proof-of-concept implementation for a new mining protocol based on stratum.

Medium-term (3-6 Months) Goals
Daemon
  • Discuss and implement new opcodes to further extend the functionality of the scriping language.
  • Implement multipeer syncing.
  • Design specifications and an implementation for a merkle tree tracking the UTXO set, to enable very fast syncing.

Wallet
  • Separate voting into its own independent process, similar to dcrticketbuyer.
  • Discuss and add basic privacy features, such as single use accounts and merge avoidance.

Scripting language and IDE
  • Have scripting language IDE functional. Integrate new opcodes into the scripting language.

Long-term (6+ Months) Goals
  • Investigate low-cost bidirectional sidechains that operate as PoS chains feeding from the main chain. Discuss the integration of other popular scripting languages or advanced privacy features on a PoS sidechain.
  • Begin integration of the Golang implementation of the Lightning Network.
  • Discuss the application of smart contracts to governance, and building a traditional corporate structure aided by smart contracts. If possible, transfer the development subsidy funds to more decentralized ownership.

Sincerely,
Decred Project

Source: Development Roadmap


Amazing! Thanks, devs!
full member
Activity: 156
Merit: 236
Hello everyone,

The developers have put forward a development roadmap for the software that details short-term, medium-term, and long-term goals. These are actionable goals, many of which already receive active development, but they are considered actionable as development activity in these directions will produce the stated outcomes, which users will see, be able to use, and benefit from in the software.

In the drafting of this development roadmap, it was important not to forecast too far into the future, so that Decred may remain versatile and adaptable to changing conditions in the field. Users can have confidence that these goals are on the developers' minds as they continue working toward them and will begin taking form as progress manifests in the different areas. Attainment of these goals will lay a very strong foundation both through the software and the project upon which to continue building and eventually expand into new areas.

All of these goals aim to work together to establish Decred as a global decentralized network and platform for accessible representation through collective voting and consensus-based decision-making on issues. And that's where it starts.

Short-term (Current) Goals
Daemon
  • Sync in the new database from btcd to prepare for voting on hard and soft forks.
  • Integrate existing Decred consensus rules into the new format inherited from btcd.
  • Demonstrate voting on a simple hardfork.
  • Clean up codebase, extend test coverage, better integrate new btcd features that were quickly merged in.
  • Clean up cryptographic libraries and remove the interface from chainec. Instead, use simple wrappers to reduce overhead.
  • Integrate latest Bitcoin softforks.

Wallet
  • Speed up calls that are heavily used by dcrstakepool, such as getstakeinfo.
  • Add new RPC functionality to the gRPC interface, preparing it for general use.

Governance
  • Make voting simple and easy to use across platforms, from the stake pool to the wallet.
  • Create a website to track voting and easily display information about voting to the end user.
  • Create the initial Decred Assembly and begin making decisions to steer development in public.

GUI
  • Finish the GUI for Windows and polish the externals for presentation.
  • Wire in stake related components of the GUI.
  • Create a one click file to setup and start the GUI, with Tor integration for connectivity.
  • Add a simple functionality to look up and update the daemon and wallet if a new version comes out.

Stakepool
  • Speed up stakepool by using asynchronous calls to the various wallets.
  • Handle situations in which the wallets are desynced without causing failure.
  • Allow external modification of the server's state, e.g. allow triggering maintenance mode.

Scripting language and IDE
  • Finalize the specifications and syntax for the scripting language.
  • Complete the initial implementation of the scripting language, with emphasis on optimization and ease of use.
  • Ensure the scripting language is backwards compatible with Bitcoin scripting, so that the entire Bitcoin-derived ecosystem benefits.

Mining
  • Get gominer functional and into production across multiple platforms.
  • Create specifications and a proof-of-concept implementation for a new mining protocol based on stratum.

Medium-term (3-6 Months) Goals
Daemon
  • Discuss and implement new opcodes to further extend the functionality of the scriping language.
  • Implement multipeer syncing.
  • Design specifications and an implementation for a merkle tree tracking the UTXO set, to enable very fast syncing.

Wallet
  • Separate voting into its own independent process, similar to dcrticketbuyer.
  • Discuss and add basic privacy features, such as single use accounts and merge avoidance.

Scripting language and IDE
  • Have scripting language IDE functional. Integrate new opcodes into the scripting language.

Long-term (6+ Months) Goals
  • Investigate low-cost bidirectional sidechains that operate as PoS chains feeding from the main chain. Discuss the integration of other popular scripting languages or advanced privacy features on a PoS sidechain.
  • Begin integration of the Golang implementation of the Lightning Network.
  • Discuss the application of smart contracts to governance, and building a traditional corporate structure aided by smart contracts. If possible, transfer the development subsidy funds to more decentralized ownership.

Sincerely,
Decred Project

Source: Development Roadmap
sr. member
Activity: 504
Merit: 250
Are there plans for a GUI wallet? Honestly, I wouldn't mind owning some decred but it's quite cumbersome to setup as it is.
sr. member
Activity: 452
Merit: 251
some sync problem with my wallet in ver 1.4 and 1.5 (with 1.3 ver this error not exist) (all daemons x32 version) 4gb ram 16gb virtual ram 4core processor 500gb free space in hard disk
dcrd.exe
12:10:55 2016-06-08 [INF] DISC: 23 addresses found from DNS seed mainnet-seed.de
cred.mindcry.org
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x582c2c]

goroutine 84 [running]:
panic(0xae8a80, 0x1179a030)
        /home/jcv/code/golang/src/runtime/panic.go:464 +0x326
sync/atomic.AddUint64(0x117f2014, 0x88, 0x0, 0x338d2398, 0xa987c0)
        /home/jcv/code/golang/src/sync/atomic/asm_386.s:112 +0xc
main.(*server).AddBytesSent(0x117f2000, 0x88, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:2099 +0x3b
main.(*serverPeer).OnWrite(0x117f0de0, 0x117c0380, 0x88, 0x338d2358, 0x11b76090,
 0x0, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:1029 +0x31
main.(*serverPeer).OnWrite-fm(0x117c0380, 0x88, 0x338d2358, 0x11b76090, 0x0, 0x0
)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:1614 +0x50
github.com/decred/dcrd/peer.(*Peer).writeMessage(0x117c0380, 0x338d2358, 0x11b76
090, 0x0, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1195 +0x442
github.com/decred/dcrd/peer.(*Peer).outHandler(0x117c0380)
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1827 +0x2d0
created by github.com/decred/dcrd/peer.(*Peer).start
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1987 +0x235
Для пpoдoлжeния нaжмитe любyю клaвишy . . .

Thank you for reporting this. This was just fixed in dcrd master, so you'd need to compile from source. This issue only affects ARM architecture. That is (detailed instructions here):

Code:
go get -u github.com/decred/dcrd/...
sr. member
Activity: 299
Merit: 250
some sync problem with my wallet in ver 1.4 and 1.5 (with 1.3 ver this error not exist) (all daemons x32 version) 4gb ram 16gb virtual ram 4core processor 500gb free space in hard disk
dcrd.exe
12:10:55 2016-06-08 [INF] DISC: 23 addresses found from DNS seed mainnet-seed.de
cred.mindcry.org
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x582c2c]

goroutine 84 [running]:
panic(0xae8a80, 0x1179a030)
        /home/jcv/code/golang/src/runtime/panic.go:464 +0x326
sync/atomic.AddUint64(0x117f2014, 0x88, 0x0, 0x338d2398, 0xa987c0)
        /home/jcv/code/golang/src/sync/atomic/asm_386.s:112 +0xc
main.(*server).AddBytesSent(0x117f2000, 0x88, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:2099 +0x3b
main.(*serverPeer).OnWrite(0x117f0de0, 0x117c0380, 0x88, 0x338d2358, 0x11b76090,
 0x0, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:1029 +0x31
main.(*serverPeer).OnWrite-fm(0x117c0380, 0x88, 0x338d2358, 0x11b76090, 0x0, 0x0
)
        /home/jcv/code/go/src/github.com/decred/dcrd/server.go:1614 +0x50
github.com/decred/dcrd/peer.(*Peer).writeMessage(0x117c0380, 0x338d2358, 0x11b76
090, 0x0, 0x0)
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1195 +0x442
github.com/decred/dcrd/peer.(*Peer).outHandler(0x117c0380)
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1827 +0x2d0
created by github.com/decred/dcrd/peer.(*Peer).start
        /home/jcv/code/go/src/github.com/decred/dcrd/peer/peer.go:1987 +0x235
Для пpoдoлжeния нaжмитe любyю клaвишy . . .

hero member
Activity: 916
Merit: 500
Already a new release, so much work done!
The Decred dev team never ceases to amaze.
Kudos!

Now we know what the future holds for Decred with this amazing team.
legendary
Activity: 1092
Merit: 1000
Hyperspace snail
legendary
Activity: 966
Merit: 1001
Yes i agree, hard working team, waiting for new releases Smiley
legendary
Activity: 1118
Merit: 1004
Already a new release, so much work done!
The Decred dev team never ceases to amaze.
Kudos!
full member
Activity: 156
Merit: 236
This development dispatch covers work completed since the Decred v0.1.4 release from May 27th, 2016. Since then, developers have merged 58 pull requests of code into 6 software repositories. During this period, a total of 53 commits occurred in these repositories and represent modifications to the effect of 9,220 lines of code added to and 4,481 lines removed from the Decred codebase.

Two additional stake pools have also come online to support the network (in alphabetical order):

Binaries: https://github.com/decred/decred-release/releases/tag/v0.1.5

dcrd
  • Synced a large number of fixes, improvements, and optimizations from upstream through November (223-26a3200, 229-08f7b6b), December (230-fe65e81, 231-77b2c53, 235-e433c18) 2015, and January (240-e190b7f, 243-1c4314e, 244-7d4646c, 246-0aeccc0, 253-6febb7b, 255-16a5842, 256-4e878a8), 2016
  • Introduced the concept of a new interface named TxSource which aims to generically provide a concurrent safe source of transactions to be considered for inclusion in a new block. This is a step towards decoupling the mining code from the internals of dcrd. Ultimately the intent is to create a separate mining package (225-9031d85)
  • Introduced a new mempool config in preparation of moving mempool to its own package (226-d73e576)
  • Created a skeleton mining package as a step towards decoupling mining code to ultimately house all of the code related to creating block templates and CPU mining (227-42550a5)
  • Added DisableRelayTx to config to set a value in the version message which informs the remote peer on whether to send inv messages for transactions (228-f0389a3)
  • Simplified PushAddrMsg to ensure that all addresses have an equal chance of being included in the addr message and moved the pseudorandom number generator seeding to package level so that it can be overridden for testing if required (232-c9c32d5)
  • Cleaned up wire code (233-c44f08b)
  • Improved test coverage (236-18e35fe)
  • Optimized the filter address handling code in the RPC server (237-d1d65c7)
  • Improved JSON RPC consistency (238-164f677)
  • Fixed ticketfeeinfo sorting (239-33bcf33)
  • Implemented a sendheaders command to request that a peer send header commands instead of inv commands when announcing new blocks (241-1cb038c)
  • Consolidated several public methods to make the creation of inbound and outbound peers more homogeneous (242-0d67c15)
  • Implemented banning based on dynamic scores. Dynamic ban scores consist of a persistent and a decaying component. The persistent score can be used to create simple additive banning policies. The decaying score enables the creation of evasive logic which handles misbehaving peers (especially application layer DoS attacks) gracefully by disconnecting and banning peers attempting various kinds of flooding. Dynamic ban scores allow these two approaches to be used in tandem (245-e3c5cd5)
  • Added a logger message containing the time it takes to process a block (247-e47d83c)
  • Modified the peer package to add support for the sendheaders protocol message (254-208eaba)
  • Prevented nodes from repeatedly requesting and rejecting the same transaction as different peers inv the same transaction (257-5125078)
  • Simplified block template exports (258-2ad0b1a)
  • Optimized map limiting in the block manager to improve efficiency (259-c21db7a)
  • Modified the chaincfg package to register the default network params via the init function instead of manually hard coding their data into the maps. This is less error prone when adding new default networks (260-d6ac2f0)
  • Consolidated tests into the chaincfg package (261-848d9fc)
  • Created mempoolPolicy to configure the mempool policy and decouple the values from the internals of dcrd to move closer to a mempool package (263-157d1cd)
  • Fixed an issue that often caused slow processing of calls through the block manager (265-eda86f5)
  • Created a new internal package for fast access to live tickets (roughly 14x faster access) (266-92635a4)
  • Added rescan and scanfrom options to importprivkey and importscript (267-63fc4e7)
  • Updated documentation (234-3117ae7, 248-2030b4d, 252-8a9956d, 262-9b3e7d7), formatting (249-d3ef588), naming (250-70f6de8), and versioning (268-b869593)

dcrwallet
  • Removed unused functions (256-8eebdff)
  • Fixed an issue where transactions were previously removed in the forward order when rolling back a block, which may cause transaction faults if there are transaction chains. Instead, roll back in the reverse order (263-3e31373)
  • Added new optional resyncing options to importscript and importprivkey for convenience. A rescan height can be included as the last argument so that the user can easily rescan from a height that is not the genesis block (264-3942d8b)
  • Updated versioning (265-cc02f1b)

dcrrpcclient
  • Added gettickets to the wallet RPC client handlers (26-65f9d22)
  • Added rescan options for importprivkey and importscript (27-f3c620d)

dcrutil
  • Added AmountSorter used by the median function in ticketfeeinfo (12-4a3bdb1)

dcrticketbuyer
  • Set HTTP server to localhost only by default (3-cef1a81)
  • Fixed an issue where the fee from a difficulty window could incorrectly return as zero if the first window was the newest, incomplete window and there were not any new tickets in that window yet. This has been corrected by checking for the size of the first window, and also by skipping any zero fee windows (5-e30f1c5)
  • Added the ability to choose which price average to use. Before, the user could only use the average of the pool price and the VWAP price for the ticket average price if not specifying
    a price target. Now users can select the mode of their choosing using the avgpricemode flag, and also the number of blocks to use in the calculation of the VWAP (6-700ecd3)
  • Added a warning on startup if the wallet is not connected or unlocked (7-5cc29df)
  • Updated configuration and fixed an unlikely simnet panic (8-65641c4)

dcrweb
  • Rewrote the landing page, made it cleaner, smaller, and SEO friendly (4-1b17a2d)
  • Added a stake pool finder utility and caching infrastructure for the block height display (5-)
  • Added the latest stake pools to the finder utility (6-53c795a)
hero member
Activity: 692
Merit: 501
฿E YOUR OWN ฿ANK
anyone else experiencing issues on yobit?

i have 80 dcr withdraw stuck for 2 days now...

Hi there. Guys and at first DEVTEAM can you connect with Yobit admins and turn on DCR wallet? Its show Wallet status: Maintenance not first day in a row ppl who are sending coins on Yobit address open support tickets but not get any answers on it. All another exchanges not have same issues with your wallet. DEV help here to solve that issue plz, its needs not only guys who are not getting their deposits. Hope you  help your miners( they are too part of your community). Ty for attention.

Anyone have a contact at Yobit? Withdrawals have not been being processed for over 36 hours and the support ticket I opened has gone unanswered for 24 hours.

The great innovation that DCR has is that exchanges can not participate in POS with out buying tickets.  And if they do, they will not have the DCR for when user withdraw.

Which could explain why yobit withdrawals haven't been going out for over 48 hours.

Just over 30 hours waiting for the removal of yobit...

I've also some problem to withdraw my DCR from yobit, not a long time (about 6h) but other users in trollbox claim that they don't be able to withdraw DCR.

I hope you will talk with yobit and try to delist DCR from that exchange, stay there isn't a good PR IMHO

More than 24h ATM.

I warn you all: DON'T TRADE @ YOBIT

3 Days and still 0 conf.

I've opened a SCAM accusation thread, if someone would like join the discussion:
https://bitcointalksearch.org/topic/resolved-yobit-scammed-me-and-not-only-during-dcr-withdraw-1500951

EDIT: issue resolved
legendary
Activity: 1316
Merit: 1021
2009 Alea iacta est
can anyone tell me the possible hashrate from 7950 AMD gpu with claymore dual miner ?


18m no OC.....
legendary
Activity: 2688
Merit: 1240
I have added a second server for stratum enabled mining @ suprnova, you can use

stratum+tcp://dcr.suprnova.cc:2254
as well as
stratum+tcp://dcr.suprnova.cc:2252

for current ccminer (old-style stratum)

and

stratum+tcp://dcr.suprnova.cc:2255

for nicehash rentals and nicehash's sgminer.


Pool @ https://dcr.suprnova.cc

Let me know if you have any problems.
legendary
Activity: 1050
Merit: 1001
is wallet for windows ready for use?
full member
Activity: 165
Merit: 100
how many staking pools are there? which is the biggest/best?

The https://dcrstats.com/ site shows you the pools and their statistics at the bottom of the page.

Thanks for that! Does polo and those pools still accept deposits initial ico coins via seed importing? Or was that bluetrade that did that? I can't remember now. I've never moved my airdrop coins

I dont think any exchange did that ... u gotta import the seed into your wallet first, to access the coins.
sr. member
Activity: 264
Merit: 250
how many staking pools are there? which is the biggest/best?

The https://dcrstats.com/ site shows you the pools and their statistics at the bottom of the page.

Thanks for that! Does polo and those pools still accept deposits initial ico coins via seed importing? Or was that bluetrade that did that? I can't remember now. I've never moved my airdrop coins
Jump to: