 Show Posts
|
|
Pages: « 1 2 3 [4]
|
|
there is no database to mess up ... this is after compiling a brand new pull from git, disabling the gui, and disabling the upnp support.
not sure what database there is to mess up ...
|
|
|
|
|
i never started a wallet -- only running a daemon on a remote server. wallet doesn't exist when you first start the program and run the daemon.
i did a `touch wallet.dat` to temporarily create the file so that the boost copy error would be gone. as souch, my wallet.dat is empty.
if i don't do that, you get the following in the debug
2016-06-19 19:51:53 Failed to create backup boost::filesystem::copy_file: No such file or directory: "/home/customer/.Syndicate/wall
et.dat", "/home/customer/.Syndicate/backups/wallet.dat.2016-06-19-19.51"
so you see that the code is trying to copy a non-existent file and tells you the problem in the debug file.
other errors are the same if i remove folder and try again.
note that the db.log file shows the following
replication requires locking support
|
|
|
|
|
i should have all the dependencies installed. i've got about 10 other coins staking on this server.
set the locations of bdb, boost, and, openssl, like i did with the other coins in the makefile.unix file and set upnp to off.
not sure what else i could be doing wrong.
boost 1.57.0
bdb 4.8 ++
openssl 1.0.1t
all manually installed and configured
no other coin has an issue with this setup
|
|
|
|
|
Trying to set up a headless daemon on my server.
Getting the following in the debug file :
2016-06-19 17:28:57 Syndicate version v1.0.0.1 (2016-06-15 16:54:08 -0700)
2016-06-19 17:28:57 Using OpenSSL version OpenSSL 1.0.1t 3 May 2016
2016-06-19 17:28:57 Default data directory /home/customer/.Syndicate
2016-06-19 17:28:57 Used data directory /home/customer/.Syndicate
2016-06-19 17:28:57 Creating backup of "/home/customer/.Syndicate/wallet.dat" -> "/home/customer/.Syndicate/backups/wallet.dat.2016-06-19-17.28"
2016-06-19 17:28:57 init message: Verifying database integrity...
2016-06-19 17:28:57 dbenv.open LogDir=/home/customer/.Syndicate/database ErrorFile=/home/customer/.Syndicate/db.log
2016-06-19 17:28:57 ERROR: CDB() : error Invalid argument (22) opening database environment
2016-06-19 17:28:57 Moved old /home/customer/.Syndicate/database to /home/customer/.Syndicate/database.1466357337.bak. Retrying.
2016-06-19 17:28:57 dbenv.open LogDir=/home/customer/.Syndicate/database ErrorFile=/home/customer/.Syndicate/db.log
2016-06-19 17:28:57 ERROR: CDB() : error Invalid argument (22) opening database environment
2016-06-19 17:28:57 : Error initializing wallet database environment /home/customer/.Syndicate!
2016-06-19 17:28:57 Shutdown : In progress...
2016-06-19 17:28:57 StopNode()
2016-06-19 17:28:57 Verifying mncache.dat format...
2016-06-19 17:28:57 Loaded info from mncache.dat 0ms
2016-06-19 17:28:57 masternodes: 0, peers who asked us for masternode list: 0, peers we asked for masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0
2016-06-19 17:28:57 Writting info to mncache.dat...
2016-06-19 17:28:57 Written info to mncache.dat 33ms
2016-06-19 17:28:57 masternodes: 0, peers who asked us for masternode list: 0, peers we asked for masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0
2016-06-19 17:28:57 Masternode dump finished 34ms
2016-06-19 17:28:57 Shutdown : done
|
|
|
|
|
Great to see this come to fruition!
Can anyone tell me if the BRK Chips in the Breakout Poker will be convertible to BRK at some point -- or is that all for testing purposes now ? I know some of the BRK Coin / BRK Twitter / BRK Owner / BRK Facebook have BRK coins in addition to BRK chips that will be given to players, but are all these chips going to be able to be converted when the platform is live? I saw on the facebook page that 1 BRK = 100 BRK chips.
Great poker platform. Playability is smooth!
|
|
|
|
Things have been quiet, I'll offer a few suggestions that maybe the devs could offer bounties for?
1. New logo, branding, etc.
2. New website
3. IRC/Twitter/Slack tipbot
4. Signature campaign
5. Blog articles, etc.
In addition, more frequent communication w/ the community would go a long way. Just my 2 EC.
Great ideas! I'm looking forward to see where this is going. The logos that were posted by one of the other members was pretty nice looking. What happened with that? |
|
|
|
|
@LISKHQ,
Is voting from multisignature addresses supported? If so, is it standard M of N?
Thanks.
|
|
|
|
|
Also looking to buy. I'd buy .2 btc worth for ~40k. PM with your best offers.
|
|
|
|
wow, i leave this thread for a few days after politely commenting on a potential flaw regarding an implementation due to lack of mathematical sophistication, acknowledgement of where to find the code and having looked at it to say that the conversation on github is more civil than here, only to find my comment removed.
discussing math and its proper implementation must be too hard.
clearly the devs know more math than anyone else and solidly refute sound mathematical proofs.
if anyone wants to have a go and find out about me before my comment gets removed again, PM me and i can send along my gpg credentials.
Maybe you just quoted an asshole in your reply? I dunno. But since you are late to that conversation by at least a full day or two, allow me to fill you in. SDC paid out the bounty. SDC has a fix they are set to release that sounds pretty neat. If you have any questions, feel free to join the slack chan to ask about the fix. I am sure those dudes would love to talk to you about the specifics. Adios muchacho. Quite possibly I quoted an asshole. But ... what strikes me odd is that someone quoted me immediately afterwared and their comment (with my comment missing) was gone. So, clearly it's a failed recursive delete as the next person's comment that included a quote from some asshole was not deleted. Either that ... or arbitrarily deleting comments was the rule of the day. Slack? Sure. I love a good math-chat. And am quite interested in the fix and why the shrugging off of the math. As for the newly noted topic summary that I see now ... edu-online: For the record: the only posts that have been removed are those of newbie accounts that are clearly set up to spread FUD. Anyone else is absolutely free to share their opinion. Just do it on your main account and in a polite and respectfull way. There have been people creating new accounts over and over. Talking, quoting and replying to themselfs to disrupt normal conversations between our users. I'm sorry but thats something we will just never accept. For the past days, it has become very clear to us that there are many people that are trying to affect SDC's price by coming here and trashing our developers. Try to communicate in a polite and respectful way and don't set up 10 new accounts to create chaos and destroy good coversation. To those of you who really have concerns or anyone else that would like to share their opinion. Use your main account. Do not hesitate and set up a post here or contact our developers directly trough Slack. We will try to comment as soon as we can. Thanks in advance.
I never quite understood why someone who rarely posts gets accused of a sock puppet account ... clearly, date joined, and prior posts are never considered as a means to determine whether someone is bringing up legitimate concerns or is just trolling. |
|
|
|
|
wow, i leave this thread for a few days after politely commenting on a potential flaw regarding an implementation due to lack of mathematical sophistication, acknowledgement of where to find the code and having looked at it to say that the conversation on github is more civil than here, only to find my comment removed.
discussing math and its proper implementation must be too hard.
clearly the devs know more math than anyone else and solidly refute sound mathematical proofs.
if anyone wants to have a go and find out about me before my comment gets removed again, PM me and i can send along my gpg credentials.
|
|
|
|
trash
Sorry to disappoint but there was no serious attention. Shen identified the potential pitfall while working on something else decided to look at existing ring signature implementations he could find to see if any of them had the bug. Both OZcoin and Shadow seemed to have it. It's possible he missed something too, and Shadow is protected in some manner, although it doesn't really look that way (the code posted here doesn't seem to fix it). I guess we'll see after further attention is given to it. Another assumption by Smooth and Co. So he happened to be working on something else and just decided to create a blog (who's only post is dedicated to this FUD) No, he discovered the issue and wanted to write it up somewhere. That's what you do when you are a cryptographer, you write up math stuff. It wasn't really enough substance for a real paper so he put it on a blog. and reddit post The reddit post didn't come from him, and as for the rest of the "PR blast", I'll just say you are naive if you think this sort of thing isn't going to be talked about. That's just the nature of crypto. There are plenty of people commenting about bugs in Monero when we've had them. Agreed that the math doesn't justify a full paper. Glad to see that some people are attempting serious mathematical and cryptographic discussions on potential implementations (granted, it could be an oversight in thinking what the code does versus what it actually does). In the civilized world, cryptographic researchers don't call other people trolls for making honest mistakes about an implementation when the scenario is that they are trying to have an honest discussion about the potential overall problems of systems that may have a faulty implementation. * complexring goes and gets his popcorn stand I think that was meant towards OzCoin and not Shadowcash. OzCoin simply stole some work without crediting/referencing, hence. Also, one should read the discussion here: https://github.com/shadowproject/shadow/issues/25#issuecomment-183024476Perhaps makes things more clear. Thanks! That does make things more clear. Looks like github comments is a much more civilized world than here. Go figure.  |
|
|
|
trash
Sorry to disappoint but there was no serious attention. Shen identified the potential pitfall while working on something else decided to look at existing ring signature implementations he could find to see if any of them had the bug. Both OZcoin and Shadow seemed to have it. It's possible he missed something too, and Shadow is protected in some manner, although it doesn't really look that way (the code posted here doesn't seem to fix it). I guess we'll see after further attention is given to it. Another assumption by Smooth and Co. So he happened to be working on something else and just decided to create a blog (who's only post is dedicated to this FUD) No, he discovered the issue and wanted to write it up somewhere. That's what you do when you are a cryptographer, you write up math stuff. It wasn't really enough substance for a real paper so he put it on a blog. and reddit post The reddit post didn't come from him, and as for the rest of the "PR blast", I'll just say you are naive if you think this sort of thing isn't going to be talked about. That's just the nature of crypto. There are plenty of people commenting about bugs in Monero when we've had them. Agreed that the math doesn't justify a full paper. Glad to see that some people are attempting serious mathematical and cryptographic discussions on potential implementations (granted, it could be an oversight in thinking what the code does versus what it actually does). In the civilized world, cryptographic researchers don't call other people trolls for making honest mistakes about an implementation when the scenario is that they are trying to have an honest discussion about the potential overall problems of systems that may have a faulty implementation. * complexring goes and gets his popcorn stand |
|
|
|
|
thanks so much. i didn't know that you could look back on the commit pages to get older versions. much appreciated.
|
|
|
|
|
Hi devs,
I am looking for an older version of the secp25k1 cryptographic library, circa July 2015. There are some old altcoin projects that use the older library and I am trying to compile them from source. Unfortunately, I can't find a copy of this older library anywhere!
Does anyone have one and / or know where I can find it?
Thanks,
ComplexRing
P.S. mods, I am unsure if this is a good place for this. But, I thought it may get the attention of some devs. I am sure there are many other people who might want this old library as well.
|
|
|
|
Good to see this actually happening and receiving positive support from the community. |
|
|
|
Is that a baseless accusation?  It looks like they are User Issued Assets (UIAs) on the BitShares platform. Perhaps they are backed by actual BKS ? Did you bother to contact the issuer of that BitShares asset ? I agree, that even if they are backed by actual BKS, that the holder of these would not be capable of voting on your platform. |
|
|
|
|
VERTICAL Coin indeed. Accumulation period is ending folks.
|
|
|
|
It's a fun game and there is not much to it. You just sit around and wait. In the meantime, your money that is used in the game is funding soup kitchens and other cool events by being used as backing for WorldAidCoin. Plus, the maths involved are pretty fun, too. That is, of course, unless you don't understand maths  . Fortunately, I've helped to break this down for you already! See http://ltcgeartalk.net/index.php?topic=220.msg2658#newAround to help when I can as are most anyone else. I kindly ask that you use my referral link, https://thegoldenegg.co/users/complexring?d31c905f5, for doing all that work on the analysis. |
|
|
|
Reducing the overall level of intelligence and critical attitude to the world, I think.
BMi
Bingo. Maths is the key. For an intro to some maths relevant to WAC and in particular The Golden Egg Game, see: http://ltcgeartalk.net/index.php?topic=220 . Apart from that. The biggest danger to the world are the people in charge who think they know better than everyone else and can dictate how to run your life. |
|
|
|
|
