As a community run project Dagger is always looking for new contributors to improve and drive the project forwards. Right now we’re specifically looking for developers with C, C++ and blockchain knowledge. But whether you’re interested in working on marketing, designing, programming or something else and feel like contributing to Dagger — come and have a chat with us! Our team mainly communicates through Discord, but you can message us through other channels as well. Work done on the project is rewarded on a monthly basis from our community fund. Dagger began as side project of a single developer, yet soon grew to involve crypto enthusiasts from all around the world. Join us in creating something new and interesting in the ever-changing world of cryptocurrencies.
One of our core developers Frozen has made an informative presentation about XDAG. It was made for his in person presentations, but we want to share it with everyone online as well. Check it out! Big thanks to Frozen for all his work on XDAG. Topics: Introduction, Block, Transaction, PoW, Algorithm, Transport, Security, Future plans. Download PDF
We are pleased to announce that XDAG v0.2.4 is released. XDag v0.2.4 release Github BitcoinTalk Change list: Whitelist is automatically updated from GitHub. Wallet with mining turned off sends only one share per task instead of six. Inactive connections (connections which do not send shares at all) are automatically disconnected after 5 minutes of inactivity. New command disconnect: allows pool-owner to manually disconnect a miner. Main network and test network are protected against accidental merging. Command history and auto-completion for Mac and Linux console wallets has beed added. Bug with payments to miner which was disconnected long time ago is fixed. Description of disconnect command: this command allows to disconnect some or all connections depending on parameters. disconnect all - disconnects all connections disconnect ip <IP> - disconnects all connections with specified IP disconnect address <ADDRESS> - disconnect all connections with specified address
The up-to-date version of Pool Owners’ Agreement can be found on our Wiki. Due to the recent events the following recommendations and decisions have been made by the community and developer team. Only use pools listed in the whitelist. Even though it’s very restraining in its current state, using only approved pools is vital for the health of the network. For now, every submission regarding whitelist addition will be audited, and only one pool will be added to whitelist per week. This will continue until the network is fully stable. The following requirements have to be fulfilled in order to apply for a pool: No private pools A public frontend would be appreciated. If you don’t want to add one, please provide at least: Pool state must be exposed in real time (maximum interval time: one minute) by HTTP. Pool stats must be exposed in real time (maximum interval time: one minute) by HTTP. Pool net conn must be exposed in real time (maximum interval time: one minute) by HTTP. Server time zone must be set to UTC time zone. Must use ntpdate to synchronize time. Must use root or unlimited user (max open files limit set to more then 4096) to start pool process. Do not try to change the hardcode of max miners. Server configuration with 8-core CPU, 32G RAM, SSD raid0/raid10 and above. 1Gbit/s Internet Speed and above. Do not block other pools to synchronize. The contact person of a pool must be added to the Discord poolowner group. Regarding whitelist additions, please send your requests to: firstname.lastname@example.org. No other ways will be accepted for now. In your email request, please include this list and fill out everything. 1 Pool IP: 2 Pool Configuration: 2.1 Pool config: 2.2 NTP config: 2.3 Timezone config: 3 Pool hardware configuration: 3.1 CPU: 3.2 RAM: 3.3 Disk: 3.4 Internet bandwidth: 4 Pool frontend: 4.1 State through HTTP: 4.2 Stats through HTTP: 4.3 Net conn through HTTP: 4.4 Pool frontend link (optional): 5 Pool Owner: (Discord username is better for communication.) You will receive invitation to join Discord from email@example.com. Tips: Please use UTC time and sync time on pool server with nearest source from http://www.pool.ntp.org/ ntpupdate -s servername Please use cat /proc/cpuinfo to get CPU info. Please use cat /proc/meminfo to get RAM info. Please use ulimit -a to get max open file info. Please use timedatectl get to timezone info. Please modify /etc/security/limits.conf to set open file limit. Example: soft nofile 65536 hard nofile 65536 state is xdag command, export this information at least once per minute. echo -e "state\nexit\n" | ./xdag -i > state.txt stats is xdag command, export this information at least once per minute. echo -e "stats\nexit\n" | ./xdag -i > stats.txt net conn is xdag command, export this information at least once per minute. echo -e "net conn\nexit\n" | ./xdag -i > netconn.txt The public HTTP access links should be like these and updated at least once per minute: http://pool.xdag.us/state.txt http://pool.xdag.us/stats.txt http://pool.xdag.us/netconn.txt Please set your firewall or iptable correctly for other pools to connect.
Dear community, the rewards for the months of April and May 2018 have been decided. The rewards are based on Github contributions and notable community involvement. Transaction ID’s are linked to each name. For their constant help and daily involvement in the development of XDAG and its core code, the following people are rewarded 26666 XDAG (53332 in total): Evgeniy Frozen For their constant help and daily involvement in the marketing development of XDAG, the following people are rewarded 6666 XDAG (13332 in total): Mathsw Sgaragagghu For helping out others on our social channels, completing light development tasks, or generally contributing to the development of XDAG, the following people are rewarded 5000 XDAG (45000 in total): rubencm (Discord help/light code task) 13ecause (Discord help) hughchiu (CN telegram maintainer) merklin (Discord help) cyan_inf (Facebook page maintainer) Jimmy (Web-dev and marketing) mojs (Code) true (Discord help and code) n8 (Telegram bot maintainer) Combined total: 111664 XDAG. Thank you everyone for being a part of the community and contributing to XDAG’s progress.
We are pleased to announce that XDAG v0.2.3 is released. XDAG v0.2.3 release Github Change list: Bug with payments caused by invalid miner addresses is fixed. Optimization in the pool logic. Convertion from hash to address made thread-safe.
Support The Community: This site is managed by the XDAG community.
You can find us in the following channels