There isn't enough liquidity for me to dump my bag (not that I would want to)

My statement was based on market analysis.  If you don't think my analysis is accurate, I would like to hear why (looks like you don't understand TA).

Do you think it's possible for the PoS ticket to get under ~6 DCR soon? It whould make a huge difference for my newly acquired (supersmall) DCR fund 

Anywhere between 10 to 20 DCR can still be considered a bargain ticket price. 

sorry i thought i was in sapnish thread..
well ,i find dcr too difficult for general users  without a solid informatic skills.
i want to stake in a pool , but i dont know what to do . i just have some dcr , in bleutrade, and that's it ,
any1 can help me please . or link me to a step by step dummies guide or video?
please thank you in advance

Can someone explain the basics of these PoS tickets?

This development dispatch covers work completed since the Decred v0.0.8 release from March 18th, 2016. Since then, developers have merged 21 pull requests of code into 3 software repositories. During this period, a total of 25 commits occurred in these repositories and represent modifications to the effect of 8,622 lines of code added to and 13,221 lines removed from the codebase.

A new request for proposal (RFP) has been opened to establish and operate additional stake pools in a number of geolocations. Several parties have stepped forward, and the project is working with them to set up the new infrastructure. Design deliverables for RFP-1 are nearing completion, the first component of RFP-4 is complete and will be integrated into a documentation system in the future, and a number of milestones are being completed and put into Decred repositories for RFP-5. Work continues on RFP-1 through 6. Finally, Paymetheus, the Windows wallet GUI for Decred has been made available as a testnet pre-release prior to the completion of RFP-1's improvements.

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

dcrd

• Added new IsUnspendable function required for the latest dcrwallet sync that takes a public key script and returns whether it is spendable (96-5fcef8a)
  
• Removed an extraneous check (98-7a15800)
  
• Updated versioning (97-5fcef8a, 99-0ed0e81)
  

dcrwallet

• Corrected and simplified shutdown logic for interrupts (127-2b79aad)
  
• Disallowed naming accounts with an empty name. Any accounts in the database that are already named the empty string are left untouched and should be renamed to something meaningful by the user (127-9fe02c4)
  
• Made wallet manage wallet database namespaces from the wallet package (127-fcccae3)
  
• Prevented a race when setting a new relay fee through the legacy RPC server (127-d09c2a8, 127-d09c2a8, 127-5d6392b)
  
• Refactored wallet transaction creation code (127-f084802)
  
• Removed legacy JSON-RPC notifications (127-6cf22b7)
  
• Updated logging for wallet locks and unlocks (127-6e6cb30, 127-71649ab)
  
• Updated startup configuration (127-cee0411)
  
• Synced dcrwallet to the latest btcwallet branch master branch. Includes general all around cleanups, pulls in new packages for improved transaction creation and fee estimation, which is now used when creating basic p2pkh transactions. Fee estimation constants and test vectors have also been updated for Decred's transaction sizes (127-2133b7b)
  
• Added a new wtxmgr API for resumable, incremental input selection that is performed under a single database transaction, and hooks up the API for transaction creation in the wallet package (130-b0aff95)
  
• Fixed updating the UTXO set for imported addresses to always update spending data even if the transaction already exists (133-a488b38)
  
• Refactored address pool code to scale to more accounts than the default account, updated address pools to be generalized so that in the future they can be multi-account, and greatly simplified logic for the address pool. Accounts are automatically resynced when the wallet is restored from seed (134-4b64adf)
  
• Removed voting pool package as it is currently unused in Decred (135-d98dc43)
  
• Ensured resync has been completed before launching notification handling so that wallet would not drop or mishandle notifications that came in synchronously when wallet resynced (136-6bf720c)
  
• Fixed proportion missed calculation in the getstakeinfo RPC request (138-1a89f7e)
  
• Increased test coverage by fixing waddrmgr tests (139-b110e4e)
  
• Modified logic for password prompting (142-5141dfa)
  
• Added safety checks for address pool access to ensure that the address pool exists and has been initialized before calls to its functions or internals (143-125bbdd)
  
• Fixed various issues identified by the static checkers (144-0c80297)
  
• Updated licensing (127-5140086), RPC naming (127-82e7437), documentation (127-397bead), and versioning (126-0d61bd9, 127-b1500ba, 150-4387fa3)
  

dcrutil

• Updated test coverage so all tests pass successfully (4-9d5a582, 6-5f2e3d6, 8-36d88d9)
  
• Updated versioning (7-9bb7f64)
  

RFPs

• Added RFP0006: Setup and Operate 10 Stake Pools (15-7bf1adb, 16-ac8847e)
  

the more people buy tickets the more expensive will get, it's pretty much like the pow mechanics and its difficulty, more people in play, more diff , which is equal to more cost to spend, now the average is 13, before was 10, so there are 33% more ticket that are bough

https://dcr.Suprnova.cc updated to latest version.

You have uploaded the wrong .asc for 0.0.9

manifest-20160304-01.txt.asc
instead of
manifest-201600401-01.txt.asc

On 0.0.8 I used "listaccounts" to see my overall balance (bought tickets included) but it now shows the same amount as "getbalance default" in 0.0.9 (the available balance without the bought tickets).
Is there another way to show my whole balance?